Would this be possible for #prioritization? I would work on it myself, but don't have any ideas for an appropriate fix.

Well, it is essentially releasing into a non-production environment. We may then want to promote the artifact from the test environment to production.

Yeah I don't know why you would want to duplicate Audit details to Maniphest. Do these commits have a single merge commit which could be audited instead?

To clarify on my terminology, my eventual goal is to have the following environments:

The cost is probably small at the moment because we are only talking about an application server, but in the future I'd expect a QA environment to consist of:

Sorry, I don't quite follow... (It's early and I'm still somewhat jetlagged... I'm in Vegas for AWS re:Invent at the moment).

I have a somewhat similar (although much more complex) use case. Basically, I want to eventually have the ability to spin up a QA environment from a diff. Currently we have developers do this manually, which means that the instances sit dormant for hours to days until the QA person is able to test it. Instead, I want to build a "Spin me up a QA environment from this diff" button into Differential. Roughly, I expect this to work as follows:

+1 on "Pipeline" instead of "Releeph".

In T9496#138811, @epriestley wrote:

I suppose we could let you disable statuses so new tasks can't be put into those states, while still retaining history for them.

Another option would be to hide transactions which would result in an "Unknown Object" being rendered, which is maybe too magical but it minimises clutter in the UI (I really dislike seeing "Unknown Object" in the UI).

Maybe the removed status should be stored in the database somewhere? That way, we can show @josh changed the status to "Blocked" and with some sort of strikethrough text or something?

Pretty sure this was only possible after the introduction of .arclint.

I can't remember off the top of my head, but I thought we had a way to pass flags to external linters. Something like this:

In T8975#138256, @epriestley wrote:

We haven't seen other requests for this and I don't think it's very straightforward. Consider these JSON values:

[{$me.phid}]
["{$me.phid}"]

The former value is not valid JSON though?

Either Phabricator should allow pulling from Inactive repositories (I see no reason to prevent pulls, but preventing pushes is probably reasonable),

In T9331#138095, @epriestley wrote:

Workarounds like the one above (or just writing similar Herald rules) seem reasonable to me, if not ideal.

I frequently use backticks in task/revision titles and would like for those to be rendered as monoscoped text, but this is a relatively small use case.

It seems that this is not limited to Maniphest, it applies to all search documents.

One issue that we constantly face is as follows...

To be honest, the paste I was archiving was a fork of another paste which I generated when I wanted to find out how forking a paste works.

Ah yeah, it seems that is the case.

No, both rules are a custom action which notifies a HipChat room.

For reference, the mail ID for @chad closed this question as resolved is 69826.

I think it would still be reasonable to default wontfix and invalid to an X, but not fussed.

+1 on this from me, but I agree that this is a duplicate of T8345.

Wontfix also has a ticked checkbox.

(It appears that this is specific to the ArcanistConfigurationDrivenUnitTestEngine)

This might be a more general issue: