Introducing the develop-catapult branch to take place of the develop branch for contribution back to Catapult. Now, your configuration will align with gitflow, a develop (localdev/test) and a master (qc/production) branch. This will set us up for cloning in Catapult rather than rsyncing it and also kicking off deployments to match deployments for changes to website repos.
Introducing the develop-catapult branch to take place of the develop branch for contribution back to Catapult. Now, your configuration will align with gitflow, a develop (localdev/test) and a master (qc/production) branch. This will set us up for cloning in Catapult rather than rsyncing it and also kicking off deployments to match deployments for changes to website repos.

calcium-machine/catapult-release-management,subinguru22/catapult,MigdaliaBrito/catapult-release-management,subinguru22/catapult,seth-reeser/catapult,seth-reeser/catapult,devopsgroup-io/catapult-release-management,stevebritton/catapult-release-management,seth-reeser/catapult-release-management,seth-reeser/catapult,calcium-machine/catapult-release-management,MigdaliaBrito/catapult-release-management,subinguru22/catapult,stevebritton/catapult-release-management,devopsgroup-io/catapult-release-management,seth-reeser/catapult-release-management,devopsgroup-io/catapult,seth-reeser/catapult-release-management,devopsgroup-io/catapult,stevebritton/catapult-release-management,devopsgroup-io/catapult,devopsgroup-io/catapult-release-management,devopsgroup-io/catapult,stevebritton/catapult-release-management,calcium-machine/catapult-release-management,calcium-machine/catapult-release-management,MigdaliaBrito/catapult-release-management,seth-reeser/catapult