Docs feedback: Runner tags examples should include more than one tag and explain if all are required
Problem to solve
The runner tagging example in the docs is too simple - a multitagging option is needed for full understanding.
A bit more detail is given here: https://docs.gitlab.com/ee/ci/yaml/index.html#tags - which implies that the job only needs a subset of runner tags to get scheduled, but not vice versa.
And example would help!
Further details
By using only one tag it is unclear if runner tags must match completely as a set for something to run.
Example 1:
Job Tag: abc, xyz
Runner Tag: abc
Does the job run? https://docs.gitlab.com/ee/ci/yaml/index.html#tags seems to say "no"
Example 2: (this is the unclear one in docs)
Job Tag: abc
Runner Tag: abc, xyz
Does the job run? https://docs.gitlab.com/ee/ci/yaml/index.html#tags seems to imply "yes"
Proposal
Provide simple examples of multi-tagged runners and multi-tagged jobs and what happens (like the above).
Who can address the issue
Other links/references
Link the doc and describe what is wrong with it.