Anything related to this phorge install, including configuration issues and sysadmin requests.
Sun, Sep 10
Seems like it is solvable via
Wed, Sep 6
Jul 31 2023
Jul 25 2023
Jul 9 2023
While Deploy Keys do not appear to be the tool, I just configured a new Personal Access Token that's tied to the PhorgeIt organization. If there are any issues, please open a new task and assign it to me, I'll take a look.
Jun 29 2023
Jun 24 2023
It's an infra issue, but it's our infra :(
Jun 7 2023
Jun 5 2023
Yeah. Maybe also test plans etc.
What is being referred to as "Public Contents"? Wiki documentation? Diviner documentation? Ponder questions/answers? Other than those I'm not sure that should apply.
May 22 2023
May 17 2023
Issue on my end, will try to get the Mysql credentials set up for running tests
Ah! That makes sense!
Running unit tests...
(Unless there's some PHP 8.2 bug in my arc invocation... )
Pretty sure, here's the full --trace output, you can see it's trying to talk to we.phorge.it (also, I see we.phorge.it in my ~/.arcrc)
I say this, since we are receiving Diffs from many other people without issues it seems:
Are you 100% sure that you are communicating with this upstream?
May 15 2023
May 1 2023
Apr 27 2023
(there used to be a "feature flags" application in Phabricator,
Apr 26 2023
I can no longer reproduce this, so I'm guessing it was something bad in my setup.
Apr 25 2023
I never tested that, but maybe we can create a couple of minimal Herald rules consisting in "Use Herald Rule H22" or similar
I've added H22, but I think at this point we should start writing code for what exactly is allowed/not allowed for these two branches.
It's also kind of annoying that there's no way to use the same rule for both repos.
Apr 7 2023
Apr 6 2023
Yeah sorry, I mis-used Projects since I was not bold enough to mark more appropriately with #Milestones (that we know are a type of Project internally)
I removed the tag from some tasks that are about Workboards and not about projects.
Projects isn't archived.
I'm still confused. I noticed that the Projects (archived) was archived since probably it was a sub-project, but why also Projects was emptied? It's a core component of Phorge, and it contained more than 3-4 Tasks inside (so, inside the avivey rule of thumb mentioned above). In this way I just feel like am I bothering you, just for trying to organize a massive work on a community project?
I'm done cleaning up Projects for now.
I'm ok with you creating a new Files tag for the Files app.
Avivey I understand your point of view, but please understand that it's really not feasible to look for "files" in the search engine, since we know in the IT everything is a file. Instead, just allowing people to click on a Tag and see some Tasks that are really related to what most looking is looking for (Files component), it's useful.
We have a really good text-search system. Just go to maniphest and search for "files", you'll get everything that's related to it.
I archived Files (archived) because there was nothing there.
If it gets traffic, we can create a relevant tag.
I disagree: I strongly suggest to keep the ability to use Projects as Tags. One problem is Mobile that affects mobile users, but it's not related to a particular area of interest like Diffusion. Also, Files (archived) , I don't agree on archiving it, since having that Tag dramatically simplifies searching for that specific topic on a search engine.
For php, eg, having a column for "8.2" under "php 8" is plenty detailed enough.
Adding lots of projects makes it harder to find the right project for a given thing.
I'm also the author of the first table here in the Change Log: