Follow-up from "Start cleaning up CI/CD variables documentation"
The following discussions from !57464 (merged) should be addressed:
-
@sselhorn
started a discussion: (+1 comment)@marcel.amirault I just checked in to see how it was going over here. If you want to address the remaining things in another MR please feel free! I think it makes sense to just have a follow-up issue that's for:
- List of variable types/names and ensure they're used consistently.
- Making sure the word "environment" is used consistently/properly.
-
@sselhorn
started a discussion: (+1 comment)@marcel.amirault I'm going to approve and ask to merge. However I have a few questions maybe you can follow-up on:
-
The topics called Project CI/CD variables, Group CI/CD variables, Instance CI/CD variables... Right now, they are written as tasks, but their titles do not reflect that--they don't start with a verb. However, the tasks seem to be the same for all three, except for a different first step, and different intro text. Could you combine these three tasks into one, with a first step that has three bullets (one for each type)? (See my next bullet.) Maybe you could actually have these topics be concepts instead?
-
What is the difference between Use CI/CD variables in scripts and Create a custom CI/CD variable in the .gitlab-ci.yml file?
-
"To view the group-level variables available in a project:" This info could be its own topic...
-