Home ▸ Migration |
---|
Migrating projects to the new branching strategies is a simple task outlined below.
Note: The process applies to release deployment projects. Any legacy continuous deployment project simply follows the instructions here.
-
Determine which branch is deployed to production.
- For illustration purposes, let's say it's
current-prod
- For illustration purposes, let's say it's
-
Merge
current-prod
intomaster
$ git checkout master $ git merge current-prod
-
Create a
develop
branch off ofmaster
if none exists$ git checkout master $ git checkout -b develop
-
Notify your team branching & release Czar so that he or she can protect the following branches:
master
develop
Github offers a feature called Protected Branches. We leverage this to make sure our core branches are safe.
To protect a branch, follow these instructions:
- Navigate to your Github repository
- Click on Settings and then on Branches in the left-hand navigation
- In the Protected branches section, configure both
master
anddevelop
branches.