Git Merge No Fast-forward Flag - Bad Practice? -
i have question regards flag can used merge command in git. apparently, if use --no-ff merge (no fast-forward flag), create new commit object @ point of merge, if merge have been performed via fast-forward.
git merge --no-ff afeature
i have not found information on flag , nobody seems discuss anywhere. bad practice create such commit object (and avoid losing information historical existence of feature)? or out of date , been replaced something?
thanks
no - not bad practice. choice have. 1 situation in forcing creation of merge commit useful in code review. if developers push feature branches review , reviewer performs merge when feature accepted merge commit contains information did review along additional comments can useful. how pull-request style workflow used github/gitlab works. when project owners accept pull request, merge commit created if capable of fast-forward merging.
Comments
Post a Comment