When you merge request and then need to make changes, at least they way i do it is git push --force to push to overwrite the branch state on remote (gitlab/github etc.)
I like that is keeps track of the diffs and changes for code review comment threads so you can see what changed inbetween multiple git push --forces to fix stuff.
That struck me the other day as not a native git feature but an actual novel thing github/gitlab do.
Or just vote here - https://fosstodon.org/@melezhik/117064923185870206
When you merge request and then need to make changes, at least they way i do it is git push --force to push to overwrite the branch state on remote (gitlab/github etc.)
I like that is keeps track of the diffs and changes for code review comment threads so you can see what changed inbetween multiple git push --forces to fix stuff.
That struck me the other day as not a native git feature but an actual novel thing github/gitlab do.
Usually once MR is merged , no need to change existing branch and people usually just create a new one to push more changes or I miss something ?