This task references more details on "Excuses" and "Prompts", but there isn't any. Is there any way to provide context around lint issues?

Any update on when this is going to reach stable? We're ~16 weeks past the earlier estimate...

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

I cherry-picked this into our fork and it fixes the problem. ✅

Is it worth noting somewhere that the V2 API uses a username and password to authenticate (and cannot use an API key) and the V3 API uses just an API key (and cannot use a username or password), and those are generated/managed in totally different parts of the Sendgrid UI? Maybe a note in the documentation?

There's demand for OpenSearch support at our installation; I have a patch that implements non-typeahead OpenSearch built and working, but I figured I'd bump the ticket in case anyone else was interested.

Having looked at the code some more, I see when the HeraldPreCommitRefAdapter runs, there is no parsed commit object yet, so there's no way to invoke harbormaster (what would the container PHID be?). This kind of makes sense.

Yeah, that was the commit that reminded me how I wanted this. Unfortunately, it looks like the database still stores literal repositoryPHIDs, so the schema would need to change if it were to handle functions (which is why I bumped the ticket instead of taking a stab at implementing it myself first). I figured I'd add my voice to the ticket for now and continue toiling along with complex Herald rules for now.

I don't suppose there's been any interest in adding wildcards/function matchers to Owners in the last couple of years?

I am also interested in this; it's not uncommon that an engineer is testing a regression somewhere and wants to trigger a full CI build of an old revision. Today, their options are (a) have admin access to the Harbormaster Build Plan, which requires a large amount of trust or (b) bother someone who does have admin access to press buttons.

I would also be interested in this feature; here's our use-case if you possibly find it more persuasive than OP's: