Differentiate between regular push and force push for audit event streaming on git operations with GraphQL
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Currently, with event streaming on git operations, the events received by a streaming destination include payloads for ssh events, http and https events, and the gitlab UI download button.
However, when a user performs a git push with the --force flag included (e.g. git push -uf origin main), the payload received is similar to one of a regular push for both ssh, http and https.
Proposal
Differentiate the payload received from a regular git push and a git force push. Currently, both payloads are identical, excluding id and created_at fields, which is expected.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.