Published: October 09, 2020 • 2 min read
I’m working on a team where we keep a clone of the development
branch (the main
place where work is done), used to deploy to a QA environment. The benefits of
this branching technique are:
clone
is isolated from workclone
is the source of truthInstead of merging, we just reset clone
to match the development
branch.
Here’s the technique:
# Update development, however you prefer.
# I like to rebase. 🤘
$ git checkout development
$ git pull --rebase
# Reset clone to match development
$ git checkout clone
$ git reset --hard development
$ git push
Deploy clone
to your QA environment, and you’ll have a working copy of
development
ready for testing.
Get better at programming by learning with me. Subscribe to my newsletter for weekly ideas, creations, and curated resources from across the world of programming. Join me today!