Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trigger new pipeline for patches that depend on a patch to be merged #84

Open
supertassu opened this issue Nov 15, 2024 · 0 comments
Open

Comments

@supertassu
Copy link

Steps to reproduce:

  • Create MRs for a stack of two patches
  • Amend the second patch, and push that
  • While the CI for the now-updated second patch is running, merge the first patch
  • Now the second patch gets stuck with a message saying "You should run a new pipeline, because the target branch has changed for this merge request."

Could Gerritlab automatically trigger the new pipeline for the second patch when merging the first patch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant