DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» is a community of 966,155 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in
Mandar Badve
Mandar Badve

Posted on

Vote: What do you prefer for parallel stories development? New branch OR New forked repo

Top comments (7)

Collapse
 
maestromac profile image
Mac Siri

If we are talking about OSS with a lot of contributors, it makes more sense for each developer to fork the repo.

Collapse
 
gsto profile image
Glenn Stovall

That's a good point! Context is important for this question.

Collapse
 
bgadrian profile image
Adrian B.G.

A new repository for a story (a group of small tasks)? That sounds like an overkill. Repositories carry some operational overhead like users, policies, pipelines and security access, and others ...

Collapse
 
mandarbadve profile image
Mandar Badve Author

I agree about the overhead. How about, developer can create her/his own personal forked repo and she/he can create pull request to it's parent repo? This way we can get rid of overhead.

Collapse
 
samjakob profile image
Sam (NBTX)

But then wouldn't they end up just using branches to prevent merge commit hell?
By which point they may as well just work on a branch on the main repo...

Plus, that approach could get kind of messy when groups of developers are working on stories.

Collapse
 
gsto profile image
Glenn Stovall

We always use new branches. Personally, I don't see any benefit to creating an entire new repo. It also makes code easier to share since we don't have to manage permissions on a per-repo basis.

Collapse
 
ben profile image
Ben Halpern

@maestromac thoughts here?

Update Your DEV Experience Level:

Settings

Go to your customization settings to nudge your home feed to show content more relevant to your developer experience level. πŸ›