On Wed, Apr 17, 2024 at 10:22 AM Antoine Musso <has...@free.fr> wrote:
> I would like to ensure CI passes before a pull request is merged. To do > so, I have added a rule to request the change to be updated (== rebased) If you mean *Require branches to be up to date before merging* then I would not recommend it. This defends against a scenario (logical merge conflict without textual merge conflict) which in practice is extremely rare, and tends to interfere with routine work. If you are still concerned, I would rather suggest checking the newer option * Require** merge queue* which offers the same safety without the downsides. > when doing a maven release:perform, the git push is refused Not if you have admin rights to the repo, though you may instead consider https://www.jenkins.io/doc/developer/publishing/releasing-cd/ which would bypass any such issues. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3ejMYnVxLuqv7oCJj9BPqX1x0Pj6TgVTFqoauyr6wZHg%40mail.gmail.com.
