Dear all, here’s yet another(?) proposal for housekeeping: Both Stylesheets and Guidelines repo feature various stale branches which I would like to get rid off [1,2]. Some of those are prefixed with a Councilists name so I encourage everyone to look through his/her branches and eventually delete outdated/unused/forgotten branches. Some of the stale branches are even just behind dev without featuring any commits *ahead* of dev (e.g. the TEI/help branch). I think those can safely be removed and would do so in the next days if no one objects. This does include release branches which I’d also like to get rid of because IMHO they do not serve any purpose anymore (the important information is kept in the tags). Best Peter [1] https://github.com/TEIC/Stylesheets/branches/stale [2] https://github.com/TEIC/TEI/branches/stale [3] https://github.com/TEIC/TEI/tree/help
I get that we can nuke branches that have the info duplicated in tags (i.e., release branches) or that have nothing to offer (i.e., have no commits ahead of dev). But for the other branches, it could be useful to keep the commit history. Is there any way to delete the branch from view in such a way that it could be recovered by the curious? And in either case (trying to keep history, and not) how does one delete a branch? ________________________________ here’s yet another(?) proposal for housekeeping: Both Stylesheets and Guidelines repo feature various stale branches which I would like to get rid off [1,2]. Some of those are prefixed with a Councilists name so I encourage everyone to look through his/her branches and eventually delete outdated/unused/forgotten branches. Some of the stale branches are even just behind dev without featuring any commits *ahead* of dev (e.g. the TEI/help branch). I think those can safely be removed and would do so in the next days if no one objects. This does include release branches which I’d also like to get rid of because IMHO they do not serve any purpose anymore (the important information is kept in the tags).
Am 10.06.2020 um 19:16 schrieb Bauman, Syd
: I get that we can nuke branches that have the info duplicated in tags (i.e., release branches) or that have nothing to offer (i.e., have no commits ahead of dev). Yes, that’s my proposal.
But for the other branches, it could be useful to keep the commit history. I wouldn’t touch these but would encourage the „owner“ to revisit this branch and whether it’s still necessary/helpful to keep it
Is there any way to delete the branch from view in such a way that it could be recovered by the curious? No, not that I know
And in either case (trying to keep history, and not) how does one delete a branch? It’s easy via the GitHub branches page: https://github.com/TEIC/TEI/branches
Best Peter
Hi Peter— I just deleted my stale branch on Stylesheets. I’ve got a couple *sort of* active branches on the Guidelines repo attached to issues that I need to continue, but I think I should rename them so they no longer contain my initials but are associated with the issues I’m working on. (And those branches require updating too.) I’ll get to that eventually! Thanks, Elisa Sent from my iPhone
On Jun 10, 2020, at 2:55 PM, Peter Stadler
wrote:
Am 10.06.2020 um 19:16 schrieb Bauman, Syd
: I get that we can nuke branches that have the info duplicated in tags (i.e., release branches) or that have nothing to offer (i.e., have no commits ahead of dev). Yes, that’s my proposal.
But for the other branches, it could be useful to keep the commit history. I wouldn’t touch these but would encourage the „owner“ to revisit this branch and whether it’s still necessary/helpful to keep it
Is there any way to delete the branch from view in such a way that it could be recovered by the curious? No, not that I know
And in either case (trying to keep history, and not) how does one delete a branch? It’s easy via the GitHub branches page: https://github.com/TEIC/TEI/branches
Best Peter
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
participants (3)
-
Bauman, Syd
-
Elisa Beshero-Bondar
-
Peter Stadler