been running into the same QOL issue here where br...
# report-bugs
a
been running into the same QOL issue here where branches can't be detected by some common CI tools. it's the biggest pain when the PR is already on main and re-running CI doesn't fix. sample logs
Copy code
Run dorny/paths-filter@v2
  ...
Get current git ref
  /usr/bin/git branch --show-current
  graphite-base/2837
Changes will be detected between main and graphite-base/2837
Searching for merge-base main...graphite-base/2837
  /usr/bin/git show-ref main
  /usr/bin/git show-ref graphite-base/2837
  <COMMIT_SHA> refs/heads/graphite-base/2837
  <COMMIT_SHA> refs/remotes/origin/graphite-base/2837
  /usr/bin/git fetch --no-tags --depth=100 origin main graphite-base/2837
  fatal: couldn't find remote ref graphite-base/2837
https://graphite-community.slack.com/archives/C02DRNRA9RA/p1746037355585019
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>
hey Alex, will check if we're tracking this internally yet. In the meantime, from that linked thread the workaround is syncing and pushing up a second time as the branches will then be pointing to their correct parent.
a
@Gareth Brickman mentioned in the post but the syncing doesn't work as a workaround if already on main afaict