Hello! Just wanted to check if you are experiencin...
# report-bugs
e
Hello! Just wanted to check if you are experiencing any ongoing issue with GitHub CI syncing. My company and I just started trial but we haven't been able to merge a single PR using Graphite due to it getting stuck on waiting for tests report. Github shows ready to merge / merged, while Graphite remains in "Waiting for CI" to finish state.
p
(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>
e
Screenshot 2025-06-04 at 11.44.42.png,Screenshot 2025-06-04 at 11.44.00.png,Screenshot 2025-06-04 at 11.43.39.png
p
hey Elder, I think it is related. Seems the underlying root cause there is either still unknown or is on GitHub's end. Could you try either of the two workarounds mentioned in there? 1. Close and then reopen in the Graphite UI, or 2. Push a blank commit up to re-trigger CI
e
Is there anything that can be done server-side to resync my company's Graphite
👀 1
p
I'm not positive- it seems to be some kind of stale state issue between Graphite and GitHub's CI check reporting
e
It's maybe related to this
Hi team, can I get someone to look into this please? There's definitely some kind of bug with Graphite where merged PRs are still showing pending CI checks. My PRs are all still impacted by this bug, hurting productivity
p
hey Elder, investigating this
Just an update that we're still not positive about a root cause here- and GitHub Actions had another outage today to further muddy the waters
e
Thank you for the update. It seems like it's resolved now!
😲 1
Sorry I was imprecise with the previous message. The github issue is resolved. The graphite issue and blocked PR issue due to branch protection checks not reporting correctly is still happening....
I opened a ticket with Github
@Gareth Brickman A few more screenshots showing that the Issue is still happening
We have gotten ourselves unstuck somehow by deleting
Classic branch protections
in Github
👍 1
Nevermind, it came back again. It was beautiful to see graphite work last night. I'm 99% sure it's Github's fault
😬 1