Skip to content
Snippets Groups Projects
Commit efbead615273 authored by Balasankar 'Balu' C's avatar Balasankar 'Balu' C
Browse files

Clarify that branches needs to be manually pushed to dev


- Explicitly call out that testing builds on dev requires
  a manual push to trigger the pipelines in the merge
  request template checklist

Signed-off-by: default avatarBalasankar "Balu" C <balasankar@gitlab.com>
parent 7973d0d1de7b
No related branches found
No related tags found
2 merge requests!67heptapod#675: making 0.31 the new stable,!66GitLab 14.9
......@@ -18,7 +18,7 @@
- [ ] Merge Request Title, and Description are up to date, accurate, and descriptive
- [ ] MR targeting the appropriate branch
- [ ] MR has a green pipeline on GitLab.com
- [ ] Pipeline is green on the [dev.gitlab.org](https://dev.gitlab.org/gitlab/omnibus-gitlab/-/pipelines) mirror for this branch if the change is touching anything besides documentation or internal cookbooks
- [ ] Pipeline is green on the [dev.gitlab.org](https://dev.gitlab.org/gitlab/omnibus-gitlab/-/pipelines) mirror for this branch if the change is touching anything besides documentation or internal cookbooks. Please note that feature branches are not automatically mirrored to dev.gitlab.org, and should be manually pushed whenever necessary.
- [ ] `trigger-package` has a green pipeline running against latest commit
### Expected (please provide an explanation if not completing)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment