GitLab
Leak events are turned into confidential GitLab issues.
How it works
Issues are created as confidential issues: leak information is visible to project members only, not to everyone who can read the project.
A single label is added, and that label is a hash of the event identifier; the identifier is not written in the clear. Duplicate prevention relies on this label.
A write is never retried automatically; on a timeout the result is marked “could not be confirmed” and no second issue is opened.
Limits
Writes go only to the named project.
Issues are not closed or deleted, and the code is not touched.
If issues are disabled or the project is archived, the connection is not established.
Setup
The setup steps are in the panel, on the integration’s own screen. What to do on the provider side and which value goes where is written there.