Merge branch 'namespace' into 'master'
Explain CI_PROJECT_NAMESPACE better ## What does this MR do? Explain CI_PROJECT_NAMESPACE better by adding "The project namespace (username or groupname) that is currently being built". ## Are there points in the code the reviewer needs to double check? Are `username` and `groupname` known words? We use it [here](http://docs.gitlab.com/ee/api/namespaces.html). ## Why was this MR needed? Because `namespace` isn't a well known term. ## What are the relevant issue numbers? ## Screenshots (if relevant) See merge request !5407
This commit is contained in:
commit
cbe787c587
1 changed files with 1 additions and 1 deletions
|
@ -38,7 +38,7 @@ The `API_TOKEN` will take the Secure Variable value: `SECURE`.
|
|||
| **CI_PIPELINE_ID** | 8.10 | 0.5 | The unique id of the current pipeline that GitLab CI uses internally |
|
||||
| **CI_PROJECT_ID** | all | all | The unique id of the current project that GitLab CI uses internally |
|
||||
| **CI_PROJECT_NAME** | 8.10 | 0.5 | The project name that is currently being built |
|
||||
| **CI_PROJECT_NAMESPACE**| 8.10 | 0.5 | The project namespace that is currently being built |
|
||||
| **CI_PROJECT_NAMESPACE**| 8.10 | 0.5 | The project namespace (username or groupname) that is currently being built |
|
||||
| **CI_PROJECT_PATH** | 8.10 | 0.5 | The namespace with project name |
|
||||
| **CI_PROJECT_URL** | 8.10 | 0.5 | The HTTP address to access project |
|
||||
| **CI_PROJECT_DIR** | all | all | The full path where the repository is cloned and where the build is run |
|
||||
|
|
Loading…
Reference in a new issue