git workflows - between forks, squash and rebase

Liran Tal - Sep 27 '17 - - Dev Community

Git is very flexible and this is what makes it great, everyone can adopt their own workflows. So without going into a flame war I'm hoping to collect some opinions:

Situation: for a SaaS product that will benefit from CI/CD, the team (4-12 engineers), working with github private repos and leveraging pull-requests to merge work from feature branches to a single master branch.

  1. what would be pros/cons for using a single repo and all the team opening feature branches in it, vs the github workflow where team members fork and work in their own repo to create PRs from.
  2. if the pull-request merge strategy is to squash (done using GH's button on the PR), then there's essentially no reason for members to rebase on their own branches if the sole purpose of it is to squash the commits.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .