question: someone on our team is expressing concer...
# how-do-ik
Kevin Walker
01/17/2024, 3:24 PMquestion: someone on our team is expressing concern about the following scenario: we have a relatively long rtunning static analysis process that blocks PRs merging in github.
so if I have a stack of 4 branches, and i click "merge" in graphite, how does that interact with github? is it 4 -> 3, rerun checks, 3' -> 2, rerun checks, 2' -> 1, rerun checks, 1 -> trunk.
because if so, that means that the merge might take upt o 4 hours to actually fold up.
✅ 1
Kevin Walker
01/17/2024, 3:35 PMokay, I think I found the relevant bit in the manual, so RTFM on me.
but can someone confirm that this is not a real concern, because graphite will do the merges bottom up (os that the CICD runs are not needing to be triggered)?
a
Aryaman
01/17/2024, 3:42 PMThe merge is bottom up.
Say you have:
4 -> 3 -> 2 -> 1 -> trunk.
We first merge 1 -> trunk, then rebase so that: 4 -> 3 -> 2 -> trunk.
Then merge 2, then rebase so that 4 -> 3 -> trunk.
And so on.
Aryaman
01/17/2024, 3:44 PMCI runs after each rebase assuming your CI is triggered on rebase & push.
We optimize to make this better in our merge queue feature, but the regular merge is automating the manual GitHub flow