catholic-emacs

6y

For a small team (<= 7 people) working on a self-managed Gitlab instance ('Starter' subscription), is it better if each user keeps a fork of the project they work on (working on other branch than master) or have everybody work on the same fork (still, different branches)?

Also, squash commits on branch merging, yes/no and why?

question

gitlab

git

Ranter

Comments

4

C0D4

66902

6y

I find it easier to work in forks, devs can ruin their fork branch history and merge into a dev/master branch (when code is ready to be pushed upstream) on the fork before merging into a staging branch (for conflicts) in the master repo.

But each team is different.
0

zotigapo

761

6y

I think you misunderstood about git.
4

Krokoklemme

4453

6y

@zotigapo then why don't you explain it?
1

dhux

242

6y

I prefer working with fork.

- If everyone is working in the same repo you will need to remove branches everytime it they get irrelevant. That is the only reason i wouldn't choose working without forks.

Related Rants

devRant © 2021 Hexical Labs LLC
Privacy Policy | Terms of Service