Added an example to doumentation for using multiple build policies with only: and except:
What does this MR do?
This MR should clear up the way only:
and except:
criteria work in conjunction. We've had a few issues opened (https://gitlab.com/gitlab-org/gitlab-ce/issues/65468 being the most recent) where people expected different behavior from except:
. The confusion and clarification are laid out in the documentation change.
Current page
https://docs.gitlab.com/12.1/ee/ci/yaml/README.html#onlyexcept-advanced
Related issues
#65468 (closed) / &1237 (closed)
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the ~Documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
/label ~Documentation
Edited by drew stachon