Update variables keyword reference style
What does this MR do?
Updates the variables
keyword reference style, and also simplifies the info a bit. A lot of the details are explained on the dedicated variables page and don't need to be repeated here.
- The
### Configure runner behavior with variables
details are duplicated at https://docs.gitlab.com/ee/ci/runners/configure_runners.html#configure-runner-behavior-with-variables, so we can delete it here (though some were missing, so copied over there for SSoT). - The prefilled variables details are all explained in detail at https://docs.gitlab.com/ee/ci/pipelines/index.html#prefill-variables-in-manual-pipelines, so we can simplify the details here, and focus just on the basic keyword details.
Related issues
- Resolves #343858 (closed)
- Related to &6565
Author's checklist
-
Consider taking the GitLab Technical Writing Fundamentals course -
Follow the: -
Ensure that the product tier badge is added to topic's h1
. -
Request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are only adding documentation, do not add any of the following labels:
~"type::feature"
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Review checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
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.
Edited by Marcel Amirault