mantidproject / mantid

Main repository for Mantid code
https://www.mantidproject.org
GNU General Public License v3.0
207 stars 122 forks source link

Add instructions for fixing a merge conflict between protected branches #37608

Open robertapplin opened 6 days ago

robertapplin commented 6 days ago

Description of work

This PR adds instructions for gatekeepers when fixing a merge conflict between protected branches (e.g. between main and release-next. The key is to make sure a PR is created to resolve the conflict, rather than pushing straight to main.

To test:

A gatekeeper should review this.

Read the instructions and build the dev docs. Will these instructions work in all cases? Was there a reason to push directly to main previously?

If fixing a conflict via a branch is a good idea, is it better to use git rebase rather than git merge? Or is git merge preferred in this instance?

Reviewer

Please comment on the points listed below (full description). Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.

Code Review

Functional Tests

Does everything look good? Mark the review as Approve. A member of @mantidproject/gatekeepers will take care of it.

Gatekeeper

If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.