Hi, .. > fantastic for fire and forget changes to a bunch of packages. You can just > make an MR and enable automerge, and not only will you be told if the
Yes, this feature is nice and is enabled by default. If you review a MR and click "merge" before the CI passed, it will hold merging until the CI actually passes. .. > I'm not sure off-hand if GitLab also has incremental and commit-by-commit > review (I would know this if I did more GitLab reviewing, but I haven't Yes, and this is how I personally always review. Unfortunately it is not the main way that GitLab promotes merging, so to start commit-by-commit review one needs to first open the "Commits" tab, then scroll down to the first commit (commits are listed in reverse chronological order) and click on the first commit. Once you get there, you see the git commit message and the changes of a single commit. It is easy to review a single commit and add remarks in this view, and when done use the "Next" button to move to next commit. > One feature I do still miss from Gerrit that I don't think GitHub has is > the ability to merge a single commit from a merge request composed of Yep, it does not. Both GitLab and GitHub approach MR/PR from the viewpoint that somebody is suggesting to merge branch X on Y, and then that branch is eventually fully merged or not (but you can configure to do the merge via --ff-only or --rebase or --squash). GitLab is not perfect, but it is what Debian ended up choosing, and 92% of packages are there, so we might as well try to get the most out of it.
