This message was deleted.
# how-do-i
s
This message was deleted.
c
@Jacob Gold and @David Bradford are doing a lot of work to improve merge!
Do you have the job ID for this example so they can take a look for you?
a
https://app.graphite.dev/github/pr/withbroadcast/broadcast/2052/Searching-for-Linear-Users Don’t have a job id but this is the pr that is at the top of the stack I was running into this issue with
j
Hi, I'll look into this one for you! I think we may have had a regression here resulting in the rebase failing.
e
I’ve been having this exact same issue as well. Haven’t been able to use the graphite “merge all” feature for a while now as it always fails after the first stack merge.
j
Hi — we've fixed some of the issues here since the original post. Mind DMing me a PR number where a merge failed?
j
Sorry for digging this up, this is a frustration of ours as well. Does the merge feature wait for CI/CD now?
j
It should! Have you run into this issue recently?
j
Gonna try it out again momentarily, just waiting on CI 😂
Well I went to test this and the second branch in my stack is stuck infinitely spinning on “Checks in progress…” when on GH the checks have already ran. When I look at the checks its waiting on, they are checks not applicable to that branch. I can make a new thread if that would be best, this may be a similar but different issue.
j
Ah, sometimes GitHub associates the wrong set of checks with the branch — there is not much we can do on our end, but adding a new commit/amending the commit on the branch will trigger a new CI run that hopefully doesn't run into this (@Ziyao Wei am I describing this correctly?)
z
Yep, that’s indeed a possibility :-) Just curious @Justin Adkins what do you mean by “they are checks not applicable to that branch”? Wondering if it could be a different issue. Also feel free to PM me the PR so I can take a look!
s
We're having a similar issue here where the check is not applicable for the second diff on the stack (but only while merging back to main).