Git, a distributed version control system, offers a variety of ways developers can integrate changes from one branch into another: git merge and gi...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for your thoughtful comment and perspective on the use of the "git --ff-only" pattern in a team setting. It's indeed a valid approach, especially in private repositories with a sizable team.
Personally, I tend to prefer the use of git rebase, mainly because it allows me to keep the changes from the source of truth, which is usually the master branch, intact while incorporating my branch. This helps in presenting a cleaner and more sequential history for me.
The preference for a linear history is a subjective matter and often depends on the specific needs and workflows of a team. The advantages you mentioned, such as a clean history, can be significant, and it's great that you find value in this pattern.