Add a DoD for Verify Engineering

What does this MR do and why?

Add an extra DoD for Verify Engineering to add working CI examples.

Resolves verify-stage#207 (closed)

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

added devopsverify documentation typemaintenance labels

assigned to @cheryl.li

/cc @DarwinJS

requested review from @jreporter and @marcel.amirault

Suggested Reviewers (beta)

The individuals below may be good candidates to participate in the review based on various factors.

You can use slash commands in comments to quickly assign /assign_reviewer @user1.

Suggested Reviewers
@grzesiek, @eread, @shampton, @fneill, @rdickenson

If you do not believe these suggestions are useful, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue: https://gitlab.com/gitlab-org/gitlab/-/issues/357923.

Automatically generated by Suggested Reviewers Bot - an experimental ML-based recommendation engine created by ~"group::applied ml".

changed the description

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/development/contributing/verify/index.md

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

Generated by Danger

FYI @grzesiek I added this to the Verify Development Guidelines. WDYT?

added Technical Writing label

added development guidelines docsimprovement labels

removed review request for @marcel.amirault

changed milestone to %15.1

approved this merge request

approved this merge request

removed review request for @jreporter

added 1 commit

• 519c3db5 - Apply 3 suggestion(s) to 1 file(s)

Compare with previous version

resolved all threads

merged

@cheryl.li, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline finished more than 2 hours ago, you should:

1. Ensure the merge request is not in Draft status.
2. Start a pipeline (especially important for Community contribution merge requests).
3. Set the merge request to merge when pipeline succeeds.

This is a guideline, not a rule. Please consider replying to this comment for transparency.

(Improve this message?)

Last pipeline passed, and the only thing left to do was to resolve a thread that had no outstanding comments.

mentioned in commit 82faedb3

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added releasedpublished label

added releasedcandidate label and removed releasedpublished label