Documentation on how to do reverts
Description
A short document describing how to do reverts for developers
I think we should have some guidance on how developers can do safe reverts, in particular between master and next. This is mostly useful if the release manager cannot help immediately.
I see two typical scenarios:
- A merge request is created and approved for both master and next, and one of the two must be reverted completely; This should be relatively simple as there is a "revert" button in gitlab, but I do not know what happens to future merges.
- A number of commits in one merge request must be reverted in master or next; Then I guess one needs to surgically remove them in both.
- do the commits have the same hash? (useful for scripting if one needs to propagate changes)
- what happens to future merges?
A related question is whether these actions must be done on gitlab or can/must be done offline in one's fork or in one's clone of the main repo.
Edited by Florido Paganelli