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
{{ message }}
This repository was archived by the owner on Jun 1, 2022. It is now read-only.
Forked from a discussion in #10; go read that if you want the full background. tl;dr: does it clutter the upstream repository if all collaborators put their development branches there? Or should contributors use their personal fork?
As I stated in #10 I'm personally of the opinion that this doesn't really matter, and branch cluttering generally isn't really a big deal (even if it does appear in the dropdown on the repo front page which was posted in a screenshot in the other issue).
Note also that when authoring a change using GitHub's web interface, it'll default to creating a branch in the upstream repo, not your fork.