Posted on
What do you prefer for parallel stories development? @github @GitHubCommunity #GitHub
— Mandar Badve (@mandarbadve ) December 17, 2018
For further actions, you may consider blocking this person and/or reporting abuse
Craftingbugs -
Yeom suyun -
Ayu Adiati -
Ben Halpern -
Once suspended, mandarbadve will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, mandarbadve will be able to comment and publish posts again.
Once unpublished, all posts by mandarbadve will become hidden and only accessible to themselves.
If mandarbadve is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Mandar Badve.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag mandarbadve:
Unflagging mandarbadve will restore default visibility to their posts.
Top comments (7)
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.
@maestromac thoughts here?