Hello! last time I was here was more than 2 years ...
# report-bugs
n
Hello! last time I was here was more than 2 years ago with another company. Glad to see you are rocking it! I have a NTH request, not a bug per se but something that is not very efficient When you push a PR it runs CI, once you add it to graphite merge queue it will run CI (even if main branch didn't change since last CI) maybe something could be done to skip that extra CI?
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 Nicolas, welcome back! In the Merge Queue settings for your repo, is the
Fast forward merge
optimization enabled?
n
Hey Gary! Yes, that is enabled
p
gotcha, I think then at this time those Merge Queue optimizations are as near to the feature you have in mind
n
Ok, I imagine as the CI is run by GHA we would have to somehow send a message to graphite saying this PR CI is running against this main branch commit. So when the PR is added to the graphite merge queue, graphite can compare the last commit on main and say, this didn't change so I can omit CI and merge straight.
Looking forward to have that at some point 🙂