Yes.
yes, unless you rebase with the --preserve-merge option, those merge commit would still be there, but without any parent on
master
.
I tend to favor the first approach because:
- it does enforce communication within the dev team
- it avoids "back-merge" (from
master
to a feature branch) - it doesn't require those merge commit from master that you would want to keep during a final rebase.
- it facilitates the final integration of that feature branch into master