I think this is basically fine as-is.

I'm going to de-scope this for now since I don't think it's terribly important, but is fairly complicated, and "v4" already has a ton of stuff in it. This should happen after UI-impacting changes like T3597 anyway.

I'm just going to merge this into T10448 since I think it's functionally identical.

When I trying to update the hosted repository from the remote GIT installed location. It is throwing following error message:
Error updating working copy: Command failed with error #255!
COMMAND
git fetch origin '+refs/*:refs/*' --prune

It helps to resolve my issue also.

I followed steps mentioned in T9213 and it resolved my issue.
Kindly close this issue.

Linters that wish to make changes should emit a line and character position (or an absolute offset), "old" text (the incorrect text to replace) and "new" text (the suggested text to replace it with) -- for script-and-regex, these are original and replacement. They should tell arc what to fix; they should not mutate the working copy themselves.

Would a "Countdown Panel" just use a saved "Countdown Query"?
If so, I'd love to be able to query only for Panels where the Countdown ends in <n days or limit the result to n items, so I can only show the most urgent Countdowns when having a lot of upcoming countdowns.

So we'd like to allow them to postpone the signature

Recent security issues in GitHub, GitLab, etc., with markdown:

One more use-case you might want to consider:

maybe mentions should always be aware of their context and prioritize users appropriately (subscribers of a task, members of a project, etc etc).

In the case of Conpherence there should be IMHO 3 "lists" considered for prioritized mentions:

1. most recent active users in the channel, so replying to one of the the latest message with a mention is straight-forward
2. members of the channel
3. global user list

Eh ... I just opened up an incognito tab and it didn't reproduce so maybe this is just something wonky on my end. Feel free to close this if it doesn't reproduce for you guys.

Totally my fault, I just didn't read half that sentence. 🐈

Thanks for looking into this so quickly.

And thanks for the report! Let us know if you run into anything else.

D17687 should dirty the cache properly on username changes. It should promote to stable within the next ~12 hours, and deploy to Phacility production about 24 hours from now.

I was able to resolve the issue by deleting my user's ssh key, and uploading the original ssh key material as a new Phabricator sshkey.

See also somewhat-related task T12397.

Not that I've geeked out about it.

Slack has the best version of Lato they home-cooked to have more letter-spacing. I wish it was open source.

It does look significantly better on secure.phabricator.com than it does on the internal version, at least to me, so I suspect the changed font resolves this.

I expect it to be better, but I don't know offhand. If it's still a problem, knowing real title cases might be helpful. It sounds like some sort of metadata is being set in the task title?

Good to know. Thanks!