Changing source/target branch breaks the merge button
Summary
Sometimes a user decides to rebase their changes to a different Mercurial branch (in mercurial-devel, a switch from default
to stable
is common when we figure out it's a bugfix for a stable release) the source branch changes, which closes the MR. The user (or anyone with permissions) can choose to change the target branch from the Web UI to revive the MR. This causes a stuck Checking pipeline status
+ greyed-out merge button with Merge blocked: all merge request dependencies must be merged or closed.
even though the new pipeline had succeeded on push.
@gracinet tells me this is load-dependent and not 100% reproducible.
What is the current bug behavior?
Pipeline status never finishes loading, merge button is greyed out wrongly warning about unmet dependencies.
What is the expected correct behavior?
New pipeline (with correct source and target branches) is attached to the MR and the merge button is usable like normal.
Details about the Heptapod instance where the bug occurs
foss.heptapod.net with:
Heptapod 0.30.2 (GitLab CE 14.8.6)
Mercurial 6.1.1 / Python 3.9.12 / hg-evolve 10.5.1