The first one is super simple – we want to remove all the references that are no longer on the remote. This can be done by executing our first clean up command:
git fetch --prune
|
Then we can remove any of the old branches that have already been merged. For that we can use the below command:
git --no-pager branch --merged | grep -Ev 'master|^\*' | xargs git branch -d
|
The first command gets a listing all the branches that have already been merged:
git --no-pager branch --merged
|
Next we need to remove the branches we want to keep. This is being done with a reverse regex
1 | grep |
(anything separated by the
1 | | |
is a or). The first one is the master branch we obviously don’t want to remove that. The next one is the branch starting with a
1 | * |
or in our case this is the branch you are currently on. Feel free to add any other branch names in here; for instance
1 | develop |
if you’re using the git flow workflow:
grep -Ev 'master|^\*'
|
Lastly we want to delete all the branches that are being printed out. This bit is simple – we can just use the
1 | git branch -d |
command and run it with
1 | xargs |
so we can pipe to the command. You may want to leave this last bit off on the first run so you can see what branches will be deleted as there is no
1 | --dry-run |
flag for this delete command:
xargs git branch -d
|
More reads
Our inaugural FedEx Day
We here at Practically took 24 hours out of client work to do our first FedEx day – so called because you deliver something the next day. We wanted to show off the creativity, technical process and breadth of what our small team made.
What is a business web application?
This Whitepaper is jointly written by Job Bains of Obsolete.com and Sam Collett at Practically.io. See more about us at the end of this document.
[diagram] Level up Cache in WordPress – a Practical Guide
Speed with websites is largely about caching of resources. We explain what, why and how we do things at Practically.