You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are currently 100 branches in the main repository. Most of these were branches for pull requests, thus contain no extra information compared to the main master branch.
When someone newly forks the project, all these branches also ends up on the fork, as well as when one works with the main account as a remote.
What needs to be done?
I would suggest considering to declutter, remove the branches that are no longer relevant. Their content will remain in the git history. I think this would provide a cleaner and smoother experience for all contributors (while I admit it would create a bit of a nuisance for those with write access and editing using the github interface, as that would create a new branch in the main repo rather than on their fork.
Who can help?
repo maintainers
Updates
The text was updated successfully, but these errors were encountered:
🎉 Welcome to The Turing Way! 🎉 We're really excited to have your input into the project! 💖
If you haven't done so already, please make sure you check out our Contributing Guidelines and Code of Conduct. If you need to connect more synchronously with members of The Turing Way community, please feel free to chat with us in our gitter channel, or you can join our Collaboration Cafe for mentored contribution or co-working.
Hi @bsipocz! Is this still relevant right now and/or being discussed by the maintainer WG? Should we keep this issue open or close it? Thanks (from the editors/reviewers WG :))
Not sure where this should/could be discussed, or who should discuss and decide on it. Maybe the only actionable item here is a more prominent highlight in the contributing guide that working from forks is encouraged, after all, I don't think we can or should enforce it.
(But the issue is almost as relevant now as when it was opened, we did a big cleanup of obsolete branches back in November, but there are still 88 left, many of which may not hold any relevant extra content, and it shouldn't really be the maintainers' task to trying to weed out the obsolete branches years after they were abandoned).
Summary
There are currently 100 branches in the main repository. Most of these were branches for pull requests, thus contain no extra information compared to the main master branch.
When someone newly forks the project, all these branches also ends up on the fork, as well as when one works with the main account as a remote.
What needs to be done?
I would suggest considering to declutter, remove the branches that are no longer relevant. Their content will remain in the git history. I think this would provide a cleaner and smoother experience for all contributors (while I admit it would create a bit of a nuisance for those with write access and editing using the github interface, as that would create a new branch in the main repo rather than on their fork.
Who can help?
Updates
The text was updated successfully, but these errors were encountered: