Here’s the request with a GitLab-style table format suitable for an issue submission: **Summary** Requesting an enhancement to the GitLab documentation to include a table mapping CI/CD variables to pipeline events. This will help users understand the availability of variables in different pipeline contexts. **What is being requested?** Add a table to the documentation that maps CI/CD variables to their availability across pipeline event types (e.g., push, merge request, trigger). Below is an example format: | **Variable** | **Push** | **Merge Request (MR)** | **Tag** | **Web** | **API** | **Schedule** | **Trigger** | **Manual** | **External** | |-----------------------------|----------|------------------------|---------|---------|---------|--------------|-------------|------------|--------------| | `CI_COMMIT_BRANCH` | ✔ | - | - | - | - | ✔ | ✔ | ✔ | ✔ | | `CI_COMMIT_TAG` | - | - | ✔ | - | - | - | - | - | - | | `CI_MERGE_REQUEST_IID` | - | ✔ | - | - | - | - | - | - | - | | `CI_PIPELINE_SOURCE` | `push` | `merge_request_event` | `tag` | `web` | `api` | `schedule` | `trigger` | `manual` | `external` | | `CI_JOB_ID` | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | **Why is this needed?** This table would provide the following benefits: - Clarity: Quickly identify which variables are available in a specific pipeline event. - Efficiency: Reduces trial and error and troubleshooting time for developers. - Comprehensive Reference: Combines variable descriptions and pipeline source contexts into a single table for easy access. **Relevant links:** - GitLab CI/CD Variables - Pipeline Events