Adding note about what variables can do

What does this MR do and why?

From a discussion in #426131 (comment 1669233840), this MR's purpose is to update our docs to say what variables can do and where they cannot be defined since includes are evaluated before jobs.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

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.

changed milestone to %16.7

added Category:Component Catalog Technical Writing devopsverify documentation grouppipeline authoring sectionci typemaintenance labels

requested review from @marcel.amirault, @dhershkovitch, and @fabiopitino

assigned to @marknuzzo

marked this merge request as draft

Hi @marcel.amirault - for your review, when you have a chance. I used a NOTE syntax to make it stand out more but please feel free to adjust.

/cc @dhershkovitch @fabiopitino

	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/ci/yaml/inputs.md (Link to current live version)

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.

If needed, you can retry the 🔁 danger-review job that generated this comment.

Generated by 🚫 Danger

added docs-only label

Setting label(s) Category:Pipeline Composition based on grouppipeline authoring.

added Category:Pipeline Composition label

added docsimprovement maintenancerefactor labels

removed review request for @marcel.amirault

mentioned in epic &7462

added 1 commit

• b6fd64ee - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

resolved all threads

requested review from @marcel.amirault

approved this merge request

@marknuzzo OK, thanks a lot, LGTM 👍

marked this merge request as ready