We're seeing that when stacks are re-pushed with Graphite, it triggers two builds for each commit in the stack, a second apart, on our CI system (Bitrise). We've contacted Bitrise, and they say that something extra is "creating/updating a GitHub

check_run

which Bitrise sees as a distinct check event and starts a build". The first build is aborted because of the second, but our CI plan has a maximum number of builds in a month, and the aborted build still counts towards the quota. Is there anything to do with how Graphite updates PRs in a stack which could cause an extra

check_run

event as well as the trigger from the branch updating?

(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>

We're using the equivalent Bitrise feature, but unfortunately the immediately cancelled build still counts towards our quota there 😞 Is there a plan for a fix on Graphite's side, or is this a fundamental GitHub issue?

It's unfortunately a fundamental GH issue