Duplicate your Development Branch for QA

- 2 minutes read - 256 words

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 work
  • It’s easy to tell what was deployed to QA– clone is the source of truth

Instead of merging, we just reset clone to match the development branch.

Here’s the technique:

# # $ $ # $ $ $ U I g g R g g g p i i e i i i d l t t s t t t a i e t k c p t c r p e e h u h e u e l c e s s d t c l l c e h e o k o k t v o n o e r u - e u l e t r t - o b e t h p a d b o c a m s e a l r e e v s m o d n . e e a n t l t e d , 🤘 o c e p h v h m e o e d l w n e o e t v p v e m e l e r o n p t y m o e u n t p r e f e r .

Deploy clone to your QA environment, and you’ll have a working copy of development ready for testing.