Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider working from branches of forks #1488

Open
bsipocz opened this issue Oct 31, 2020 · 4 comments
Open

Consider working from branches of forks #1488

bsipocz opened this issue Oct 31, 2020 · 4 comments
Labels
caretaking infrastructure For all issues related to book infrastructure

Comments

@bsipocz
Copy link
Member

bsipocz commented Oct 31, 2020

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?

  • repo maintainers

Updates

@welcome
Copy link

welcome bot commented Oct 31, 2020

Welcome Banner
🎉 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.

@EstherPlomp
Copy link
Collaborator

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 :))

@bsipocz
Copy link
Member Author

bsipocz commented Mar 16, 2023

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

@aleesteele aleesteele added the infrastructure For all issues related to book infrastructure label Oct 16, 2023
@aleesteele
Copy link
Member

Flagging this for the #2690 – as this is relevant for the working group.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
caretaking infrastructure For all issues related to book infrastructure
Projects
Status: No status
Development

No branches or pull requests

3 participants