MozillaWiki:Policies/Deployment workflow: Difference between revisions

clarify how changes are brought to production branch
(add a placeholder heading for composer)
(clarify how changes are brought to production branch)
 
Line 17: Line 17:
* [https://github.com/mozilla/wiki.mozilla.org/tree/production production] – stage → prod
* [https://github.com/mozilla/wiki.mozilla.org/tree/production production] – stage → prod


After changes are tested via the master branch on our dev server, they are merged into the production branch. This branch is deployed to stage, checked and if all is well, it is deployed to production.
After changes are tested via the master branch on our dev server, commits intended for release are cherry-picked into the production branch. This branch is deployed to stage, checked and if all is well, it is deployed to production.


== Repository layout ==
== Repository layout ==
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,698

edits