[Infrastructure] GitHub Branch Cleanup

Dimitris Zacharopoulos (HARICA) dzacharo at harica.gr
Mon Feb 3 10:00:31 MST 2020

I have some general concerns about loosing the "immutable" redline 
version that we vote on. If someone deletes a branch (private fork or in 
the cabforum), the immutable link to the redline that was voted on will 
be broken.

If this is true, then I think we need to have an improved process where 
a private fork is "copied" back to the cabforum/documents repo, and made 
read-only or something. Of course I am not a git expert so I'm asking 
here to get some reassurances that deleting branches will not create 
unintentional gaps.


On 2020-02-03 5:29 μ.μ., Ryan Sleevi wrote:
> 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?
> _______________________________________________
> Infrastructure mailing list
> Infrastructure at cabforum.org
> http://cabforum.org/mailman/listinfo/infrastructure

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/infrastructure/attachments/20200203/bb847ad2/attachment.html>

More information about the Infrastructure mailing list