Skip to content

Changes

Page history
Update WST Merge Request Process Overview authored by DAVID KUNKEL's avatar DAVID KUNKEL
Show whitespace changes
Inline Side-by-side
ADS/WST-Merge-Request-Process-Overview.md
View page @ 60bfbcb7
......@@ -2,12 +2,12 @@ Drupal developers must follow the steps below when submitting a Merge Request (M
**Developer steps:**
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. On Gitlab account, click on the link provided at the top of the Gitlab UI to setup your MR.
3. Select the `Standard` MR template for routine updates and fill out the following items:
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. Update `Assignees` (upper right corner) to the developer who will review/test MR.
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 your new updates in our non-prod environment for MR review.
2. On Gitlab account, click on the **MR setup link** provided at the top of the Gitlab UI to create your MR.
3. Select the **`Standard`** MR template for routine updates and fill out the following items:
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. Update **`Assignees`** (upper right corner) to the developer who will review/test MR.
5. Save `MR` and ping developer in MR `Comments` to start reviewing.
6. **IMPORTANT** - Update your 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.
......