Oh, I didn't see D20257. Carry on.

• Remove unused variable.

There are four separate UI feedback indicators right now:

An adjacent issue is that the current behavior of overheated queries is to return a partial result set and set a flag. The goal of this behavior is to let us show some results if we find some results, but it may be surprising if the caller doesn't handle overheated queries, since they may look like a queries which simply failed to match anything.

This is very tricky to take a screenshot of.

The hypothetical steps above do, in fact, reproduce this:

Not sure about moving this forward.

• Push fixes for null/empty behavior back to the previous revision.

• Minor fixes for null/empty behaviors.

It seems that newer versions of git have become more aggressive at detecting binary changes as moves + renames, because my install is now hitting this on a very frequent basis

Indent Depth Increased, Old:

In the future, when a board can be ordered/grouped by author or assignee (or maybe custom fields), what should dragging a card within a column do?

• Typos/spelling.

• Describe "run" and "pause/abort/resume/restart" in two different rules to get rid of weird compound clauses.

• Wordsmithing.
• Use "sent for review" over "promoted from draft".
• Use "wait for the build" over "wait for the build to complete to pass".
• Try to make "X, and/but Y" structure a little more consistent.
• Improve clarity of "land" condition.

I can't get anything remotely convincing out of ab. This or some similar change might still be a good idea, but I'll wait until I have a clearer case for it.

• Minor tidying.

I'm going to take another run at this, but from a slightly different angle.

I haven't seen any of that so far, but it seems pretty reasonable to me. Maybe I'll just add it unless I can come up with some reason why it's secretly bad in the time it takes to implement.

Does anyone want an option for "only allow builds that have failed to be restarted"? For cases where builds are idempotent except for a final irrevocable step like "find servers running any version of the code != this version and kill them"?

• Spelling.