From reading the git code, looks like there is a flag to allow this feature - uploadpack.allowReachableSHA1InWant, though I'll need to check that it actually works.

The specific set of commands im looking at are

mkdir -p phabricator_git_repo && cd phabricator_git_repo && git init && git remote add origin https://we.phorge.it/source/phorge.git && git fetch origin b11c6fcacd8bceafc2a2f223037952dc817f4d7f && git reset --hard FETCH_HEAD && rm -rf .git && true

this commit does exist https://we.phorge.it/rPb11c6fcacd8bceafc2a2f223037952dc817f4d7f
we use a build system which fetches the code from a git repo and makes it available to the next stage of the build

From a quick googling, it looks like this isn't a server configuration, but most likely the commit you're looking for just isn't in the remote.
Why are you using this command? Are you using submodules for deployment?

I mean, that's not a particularly good solution to the problem. It just makes the time for which it appears to be fixed longer (even though nothing has changed)

I would suggest increasing the TTL to a day if you are not planning on moving servers in the near future.

@avivey the one in upstream does not contain the new ISRG Root X2 CA.

I submitted D25049 for review on the 26th to address certs signed by the ISRG Root X2 root that is in the updated default.pem file.

If you view a book, then view source and search for PHID-BOOK then you should find a policy link. That's the PHID of the book you're viewing.

We've picked up an updated version of the pem at https://secure.phabricator.com/D21739 - it's not the latest, but is it recent enough?

I've written https://we.phorge.it/w/installation_and_setup/update_from_phabricator/, and I think it's basically ready for simple case (and considering we're still compatible with Phabricator in all technical aspects).

I think we're done here too? E13.

I've cowboy-merged this last week. Not sure why all these commits decided they are part of this task though?

I've tried locally with ./bin/remove , and it appears to work. To get the phid, I've visited the page and used "Actions -> Advanced -> View Handle" - I don't have this action available here.

Phorge is not yet ready. See T15014, T15023, T15026.

In T15012#2678, @avivey wrote:

I've re-generated the docs, and now we have two copies:

so:

1. need to delete the old ones, I didn't find a straight-forward way to do that
2. maybe do some http redirect from the old links to the new ones.

@avivey Thanks a lot for the hints. I will take a look at the Spaces. That sounds like it could be helpful for our purposes.
@rraval Could you or someone else verify that a project that is made visible only to Administrators still shows up when a user opens the search selection list on the Subscribers field? And is this considered to be a bug or a feature? Of course i can set up a new Task for this if that makes sense.

I've started the a draft for the Going Public announcement - {Blog Post: Going Public} - please chime in with comments...

Note the ISRG Root X2 has been added here used by Lets Encrypt.

In T15012#2679, @MacFan4000 wrote:

We should also generate the arcanist docs.

We should also generate the arcanist docs.

I've re-generated the docs, and now we have two copies:

(Regarding the original task description:)

In T15110#2655, @avivey wrote:

I'll try to force the GC to run, maybe this will delete them.

But still it is worrisome that we can configure visibility only by Administrators, yet everybody can assign the project as subscriber... Maybe that is a bug ?

@rraval Right, i overlooked this setting. I managed to hide most projects from the Subscribers Search panel. We also have reduced the number of Projects to keep things more tidy.

@Higgs You should be able to Project → Edit Details → Visible To → Project Members. Does that do what you expect?

I'll try to force the GC to run, maybe this will delete them.

We use Projects for grouping users into teams. But unfortunately every user can see all Projects and assign them as subscribers to Tasks, regardless if they are members or not. Normally (in our case) Tasks are only relevant for users in the same project. Having the other projects displayed in the subscribers selection is unfortunate in this case.

Somewhat related - see T15050

Our instance uses a ton of projects as "groups of people that need to be notified", so we use project subscribers a lot.

We do have a security task creation form and a separate space that roots have access to. See S2

• remove favicon, update css in php

Favicons are somehow cached server side:
<link rel="icon" id="favicon" href="http://localhost.localhost:8080/file/data/jvpvboup37hwjgpn3viv/PHID-FILE-xhmdncm6ydmubbkrfdj4/favicon" />

I didn't want to do this, but I'm actually going to test this change.

celerify

Could it be cached?

looks like the favicon doesn't actually work :/

For the record, I am against this change.

@speck I made this task because posts in Phame uses an ID that starts with J, and tasks in Maniphest uses T for the URL too.
I just request that the URL for posts in Phame changes to be similar to Maniphest.

Could you elaborate on what this would help with? I recall reading something in Phabricator’s past that the current url scheme is intentional as opposed to using the monogram/slug. I did a quick search and couldn’t find much, though in this change release
https://secure.phabricator.com/w/changelog/2015.51/

Removed dedicated titles/slugs. Phame posts now automatically generate readable URIs, but the slugs are no longer semantic.

We should investigate the history related to the current URL scheme before making a change. My suspicion is that it has to do with phase posts being “public” or published where having a url with part of the title is very common for linking across other content.

This task may need to be triaged as high since we started by forking the Phabricator software, see also T15006: Re-brand Phorge.

Using a repository cluster for syncing repositories to two hosts I can push fine via ssh:

We should also change the internal name to the future name of Phorge, rather than leaving leftovers. Exmaple: Some code in Fandom is still named wikia.

lint