We have a bug where a GitHub Actions Matrix job in a workflow shows as a required check despite: 1. The 3 versions of the job have completed successfully 2. The job is not a required check in the one ruleset we have in the repository

(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using

gt feedback --with-debug-context <any message>

A redacted section of the workflow file for reference. The Test Report step is a required check.

Hey William, thanks for the detailed report here! could you please share a repo name / pr number i can look into our logs for? Even better would be: if you can reproduce this consistently, could you make a test PR that you can leave in that state and then use the

Send feedback

option from in the Graphite app's Help menu (shortcut is

G

then

F

) so we have all the info needed to look into it further

Some examples from today. Repo: Feeld/core-api PRs: 3425 3429 3423

Hey William, ive been trying diligently to repro this and cannot. you can see im not getting that extra pending check for the entire matrix with just the Test Report step required.

Thank you for investigating this. Here's the json and screenshot

appreciate it, just sanity check, there is no traditional BPRs?

Interestingly I don't see a Branches option and I do have full permissions so it won't be a permission issue. Could you share the url pattern so I can try manually hitting that screen just in case? I tried calling

gh api repos/Feeld/core-api/branches/main/protection

and got

{"message":"Branch protection has been disabled on this repository.","documentation_url":"<https://docs.github.com/rest/branches/branch-protection#get-branch-protection>","status":"404"}

URL: https://github.com/{org}/{repo}/settings/branches

OMG, this did it, thank you!

🙌

I will disable but it looks like you're pulling this even when GitHub doesn't treat it as active. Bit of a nasty edge case so completely understandable.

yea im not sure how classic BPRS get disabled but can relate to a similar "hidden but not disabled" thing we have here 😅

Thanks again for the help