Tidy Up

Forge Your Future with Open Source — by VM (Vicky) Brasseur (51 / 108)

👈 Review, Revise, Collaborat e | TOC | Special Considerations for Windows-based C ontributors 👉

Now that the project merged your contribution, you no longer need that feature branch that you created. It won’t hurt anything if you leave it lying around, but it doesn’t take long for these branches to build up and make a lot of clutter. Deleting it right after your pull request is accepted not only tidies up your testing environment, but it also makes it easier to locate the branches you need later and reduces the chance that you’ll accidentally work on this now-dead branch. Removing a branch is quite easy from the command line. Here’s an example where I removed a branch from my book repository:

Note: This was a local branch. It’s also possible to push a branch to the remote origin repository. An example of a command to delete a remote branch:

Check the documentation for git for further instructions on branch use.[87]

👈 Review, Revise, Collaborat e | TOC | Special Considerations for Windows-based C ontributors 👉

Related posts:

Written by Matthew Gould, CEO, Indra Joshi, Director for AI; Ming Tang, National Director Data and Analytics, NHSX The NHS is facing an unprecedented challenge. Responding to the Covid-19 crisis will…

My first writing course taught me how to write an article and break into print. Back then, the internet was still fairly new. Magazines were one of the main avenues to accumulating clips and…

Software is full of surprises. No matter how careful or skilled you are, when you create software it can behave differently than you intended. Exploratory testing mitigates those risks. Part 1 introduces the core, essential skills of a master explorer. You’ll learn to craft charters to guide your exploration, to observe wh