On 10.07.19 13:13, José Iván López González wrote:
Hi guys,
I see we have several temporary branches in many YaST repos, for example in
yast-storage-ng:
SLE-12-SP2 tracked
SLE-12-SP3 tracked
SLE-15-GA tracked
SLE-15-SP1 tracked
feature/bsc-1123688 tracked
feature/export-stray-blk-devices tracked
feature/suma tracked
master tracked
missing-textdomain tracked
parallel_rubocop_at_travis tracked
pre-SLE-15-SP2 tracked
rtl-pathnames tracked
sle15_parallel_tests tracked
stray_blk_dev_impl tracked
suma_guided_setup tracked
suma_proposal_devices tracked
upstream/feature/partitioner-remember-tree-state tracked
A lot of this could actually be avoided:
- Create a branch in your own fork unless you need to work on the branch with
several people, then you won't clutter the upstream repo with your working
branch.
- Always prefix your branches with your nick or user name so people at least
know who to talk to. I always use "huha-something", even in my own forks and
even in my 100% own repos. Make that a habit, and there is no confusion.
- After the PR is merged, simply click on the "delete branch" link that
GitHub offers you. Once it's merged, there is no need to keep it around; and
it will stay around in your local checkout anyway until you do
git fetch --prune
or
git remote prune myrepo
Kind regards
--
Stefan Hundhammer <[email protected]>
YaST Developer
SUSE Linux GmbH
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah; HRB 21284 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
