markdown guide

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


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


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 ...


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.


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.


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.

Classic DEV Post from May 31

Presentation Tips for Technical Talks

Presentation Tips for Technical Talks

Mandar Badve profile image
I am web developer, working on Microsoft Technologies like ASP.NET MVC and Windows Azure. Have experience on JavaScript and CSS frameworks.