We're starting to see some very odd behavior from ...
# report-bugsj
Jameel Al-Aziz
03/25/2026, 3:59 AMWe're starting to see some very odd behavior from Graphite PRs that we haven't seen before. All of a sudden, GitHub is treating Graphite merge PRs as coming from a fork and is requiring us to manually approve workflow runs on Graphite merge queue PRs.
✅ 1
p
Pylon
03/25/2026, 3:59 AM(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>j
Jameel Al-Aziz
03/25/2026, 4:00 AMThis completely blocks the merge queue since various workflows are required as status checks.
p
Pylon
03/25/2026, 3:15 PMSorry for the trouble here, we can definitely take a look. Mind hitting G then F from a problematic PR? That'll send us more logs that we can dig into.
j
Jameel Al-Aziz
03/25/2026, 5:47 PMJust did.
Jameel Al-Aziz
03/25/2026, 5:49 PMAs far as I can tell, GitHub changed some behavior overnight and is now treating all bot PRs as coming from a fork 😞. I see discussions in the GitHub Community Discussion about similar behavior for Copilot and there doesn't seem to be a workaround other than enabling workflow runs from forks, which is a dangerous setting that has led to some very recent high profile incidents.
😬 1
p
Pylon
03/25/2026, 6:11 PMGotcha. We'll take a look!
2 Views