@marcan leave a comment with a line that is /rebase. Can be the only text, then it is silent and doesnโt leave a comment but rebases anyways.
Locally you git pull --rebase
If the project is configured a certain way, this shows up as a button
Top-level
@marcan leave a comment with a line that is /rebase. Can be the only text, then it is silent and doesnโt leave a comment but rebases anyways. Locally you git pull --rebase If the project is configured a certain way, this shows up as a button 3 comments
@marcan it can, but itโs a MR strategy. I forget some people want their MRs to be squashed separately from the merge process. The config I prefer as a GitLab repo owner is to do squash merges with semi linear history, and then the merge button does that for you (and you can rebase in the UI without the command). This is so easy to work with and is the best of both worlds because you can always look at the pre-squashed history in the MR. @marcan so in your case I donโt think you can do it differently, but they can configure the project to make this automatic |
@ZiggyTheHamster The goal there was the squash though (hence interactive rebase), can it do that?