[Infrastructure] GitHub Branch Cleanup
Ryan Sleevi
sleevi at google.com
Mon Feb 3 08:29:26 MST 2020
I noticed that there tends to be a proliferation of branches, particularly
for merging, that aren't getting deleted.
When folks fork the repository, this makes it even messier to keep track of
things.
I'd like to propose the following:
- For https://github.com/cabforum/documents , we delete all existing
branches
- When making edits (e.g. merging a completed/approved ballot), those edits
are done either:
a) From a personal fork, merged in via a Pull Request
b) If absolutely necessary (although very undesirable), via a temporary
branch that is similarly merged via Pull Request, and the subsequent branch
deleted after the PR has been merged in
Does this seem reasonable?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/infrastructure/attachments/20200203/5bcededf/attachment.html>
More information about the Infrastructure
mailing list