In T15712#15124, @avivey wrote:

Is the motivation only to allow not-magicking things like "S3" and "F1", or is there more?

Looks like the tickets end in a Wontfix in https://secure.phabricator.com/T5301; I didn't follow the whole thing, but often the reasoning in Remarkup boils down to performance.

Just as a reference point, a few years ago, I created a version of this as well - It supports readCoverage coverage reports, etc.

Seems like it is solvable via

What is even stranger is that theoretically, php should not be able to exit with a status code of -1 - If you try, it changes it to 255

For completeness - Landing revisions from the UI Since they wouldn't be able to land from git? - Would have to be enabled in the UI

Could this be solved with a Herald action?

Just some notes for later

No errors in the console..

In D25129#4130, @Dylsss wrote:

In D25129#4083, @aklapper wrote:

Thanks for accepting. As I have been puzzled by arc for many years now, is there a way to merge via the web UI? arc land D25129 on a shell tells me that Branch "D25129" does not exist in the local working copy, likely because I've reset stuff here.

There is no way to merge from the web UI.

In T15096#3967, @valerio.bozzolan wrote:

One thing that could help a lot for my survival, for example, is the creation of a small bot able to convert the GitHub/GitLab flow to the Phabricator flow - automagically.

So, if I have a repository mirrored to GitHub in read-only, people can just do a pull request, and their stuff is converted to an arc diff, without any intervention from the code contributor.

I only warn that I work on it, because I need it for some personal side-projects hosted in my personal Phabricator - and where I don't want to yell at contributors who send pull requests from elsewhere.

D25015 was by @dcog If it can't be fixed with an update, this should be reverted

This revision is nearly impossible to test

Just a warning that I found a few bugs just by spot checking...

Hit esc today - Lost lots of typing

We should abandon this revision as secure has already updated their pem - see https://lch.lcdevops.com/rLCARCANIST13d3a3c3b100979c34dda261fe21253e3571bc46

• ran arc liberate

Here is the commit that introduced this

This looks pretty great! - I think T15030 is the general covering task for Extensions

I can confirm as well that I have never received an email from phorge / phabricator on my email which isn't "outlook.com" but is an office 365 email account

This is what the README says - And maybe we should remove support for the default.pem altogether? (But, possibly leave support for custom.pem)