Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 23,813
    • Issues 23,813
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 861
    • Merge Requests 861
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Packages
    • Packages
    • Container Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Merge Requests
  • !20587

Merged
Opened Nov 21, 2019 by drew@drewcimino💬2 of 7 tasks completed2/7 tasks
  • Report abuse
Report abuse

workflow:rules documentation

  • Overview 21
  • Commits 3
  • Pipelines 7
  • Changes 1

What does this MR do?

This is the CI configuration reference documentation for workflow:rules #29654, and closes #36517 (closed), the documentation issue.

Related issues

  • #29654
  • #36517 (closed)

Author's checklist

  • Follow the Documentation Guidelines and Style Guide.
  • [-] If applicable, update the permissions table.
  • [-] 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

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

/label documentation

Edited Dec 10, 2019 by drew
Assignee
Assign to
12.6
Milestone
12.6
Assign milestone
Time tracking
10
Labels
Category:Continuous Integration Technical Writing backstage devops::verify direction docs-only docs::feature documentation feature group::continuous integration
Assign labels
  • View project labels
Reference: gitlab-org/gitlab!20587

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.