> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/application-security/onboard-data-sources/onboard-version-control-systems/gitlab-saas/reference-a-subscribed-events.md). # Reference A: Subscribed events Events Cortex Cloud subscribes to for GitLab SaaS. This reference lists the GitLab SaaS events that Cortex Cloud Application Security subscribes to. | Category | Event | Description | | -------- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | Projects | c | — | | — | merge\_requests\_events | This event is triggered when merge or pull requests are created, updated, merged, closed, or have changes made to them | | — | push\_events | This event occurs whenever code changes are pushed to a repository, indicating new commits being added to the version control history | | — | tag\_push\_events | This event is triggered when new tags are pushed to a repository | | — | note\_events | This event is generated when comments or notes are added to various objects within GitLab, such as issues, merge requests, or commits | | — | confidential\_note\_events | Similar to note\_events, but specifically for confidential comments or notes that are restricted to certain users or groups | | — | issues\_events | This event is triggered when issues are created, updated, closed, or have changes made to them | | — | confidential\_issues\_events | Similar to issues\_events, but specifically for confidential issues that are restricted to certain users or groups | | — | job\_events | This event occurs when jobs defined in CI/CD pipelines are created, updated, started, finished, or have changes made to them | | — | pipeline\_events | This event is generated when pipelines are created, updated, started, finished, or have changes made to them | | — | wiki\_page\_events | This event occurs when changes are made to wiki pages within GitLab, including creation, updates, and deletions | | — | deployment\_events | This event is triggered when deployments are created, updated, started, finished, or have changes made to them | | — | releases\_events | This event occurs when releases are created, updated, published, or have changes made to them | | Groups | — | — | | — | subgroup\_events | This event is specific to GitLab groups and occurs when changes are made to subgroups within a group hierarchy | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/application-security/application-security/onboard-data-sources/onboard-version-control-systems/gitlab-saas/reference-a-subscribed-events.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.