|
|
|
Follow the steps below when submitting a Merge Request (MR) for all development updates to production websites:
|
|
|
|
|
|
|
|
1. Commit code updates from local dev environment feature branch to Gitlab. This will trigger a Gitlab CI/CD pipeline to build your feature branch site with new updates in our non-prod environment for MR review.
|
|
|
|
2. Inside Gitlab, click on the link provided at the top of the Gitlab UI to setup your MR.
|
|
|
|
3. Provide the following items on your MR (as part of `Standard` MR template):
|
|
|
|
1. `Summary` - description of your update with ES story number. (e.g. STRY1234567 - update to x so that y)
|
|
|
|
2. `Steps to Test` - list of steps to test your update in your feature branch build.
|
|
|
|
4. Set `Assignees` to developer who will review/test MR.
|
|
|
|
5. Save `MR` and ping developer in MR `Comments` to start reviewing.
|
|
|
|
6. Update development story in ES portal to change state from `Work in Progress` to `Developer Peer Review` and update `Assignee` field to developer who will review MR.
|
|
|
|
7. Upon completion of MR review, developer should ping BA for final testing in MR `Comments`.
|
|
|
|
8. Developer should then update story in ES portal to change state from `Developer Peer Review` to `Testing` and update `Assignee` field to BA who will complete final review of MR.
|
|
|
|
9. |
|
|
\ No newline at end of file |
