Martin Pitt <mpitt(a)redhat.com> writes:
After a PR of mine lands, I always manually press the "Delete
branch" button,
so that "git branch -al" does not pile up cruft and remains an useful tool. I
guess/hope that most other people do the same?
(I actually don't, and looking at a list of my branches is completely
useless for me. If I need to find a branch, I rely on Github telling me
the branches with recent activity. On the other hand, I usually don't
have branches that don't have a PR, so I don't have to find branches all
that often.)
GitHub recently added a simple config option to automate that:
https://help.github.com/en/github/administering-a-repository/managing-the...
Does anyone object if I enable that for our cockpit projects?
No objections.
But, doesn't this setting apply to the origin repo of the PR? I.e.,
every contributor would have to enable that in its own fork of cockpit,
if they want. At least, that's how I would design this feature, I can't
really tell from the docs.
There is only one way to find out!