Audit log
The audit log records who did what, and when. It holds actions taken by people (sign-ins, settings, policies, votes) and actions Merge Pilot takes by itself (evaluating a merge request, opening a change approval, recording a merge).
Who can read it
| Role | Audit log |
|---|---|
| Platform admin | Every company's entries, and the platform's log |
| Company admin | Their own company's entries |
| Auditor | Their own company's entries |
| Policy manager | No access |
| User | No access |
The page is under Administration → Audit log in the sidebar. It is hidden from roles that cannot read it. See Roles and users.
Nobody can edit or delete an entry, from the page or the API. Merge Pilot removes entries only once they are older than the company's retention period (see How long entries are kept).
What an entry holds
| Column (label in the UI) | What it shows | API field |
|---|---|---|
| Time | When the entry was written, shown as a relative time | created_at |
| User | The person who acted. Actions Merge Pilot takes by itself show merge-pilot | username |
| Action | The action name, for example policy_updated (see Audit actions) | action |
| Resource | The kind of object acted on, for example merge_request, policy, user | resource |
| Resource ID | The ID of that object | resource_id |
| Status | success or failure | status |
| IP | The client IP of the request. Actions Merge Pilot takes by itself show system; entries written by a bulk operation show the address it was started from | ip |
Click a row, or its arrow, to open its details (details):
- When an entry records a change to settings, the details show What changed: one line per changed field,
field: before → after. - Secrets are never shown. A changed password, secret, token, private key, API key, client secret or webhook URL appears as
********on both sides. - Other details (the policy name, the change approval key, the reason of a failure, and so on) are shown as they were recorded.
The newest entries come first. Time, User, Action and Status can be sorted by clicking their headers. The page shows 20 entries at a time.
Filters
| Filter (label in the UI) | What it does | API parameter |
|---|---|---|
| Search username or action | Finds entries whose user name or action contains the text, ignoring case | q |
| Action | One action. The list offers All actions and a selection of common actions; to find any other action, type its name in the search box | action |
| Status | All statuses, Success or Failure | status |
| Resource (under More filters) | One kind of resource. The list offers All resources, Project, Group, Project variable, Group variable, Branch, Merge request, Webhook, Company, User, Settings and Change policy | resource |
| Username (under More filters) | The exact user name | username |
| IP address (under More filters) | The exact IP | ip |
| From date, To date (under More filters) | Only entries from this day, and up to the end of this day | from, to |
Clear all resets every filter.
Which company's entries are shown
The page shows the entries of the company selected in the company switcher.
Some entries belong to no company: they are in the platform's log. They are marked Platform in the Audit actions tables, and are also written for platform admins' own accounts (their sign-ins, profile and password) and for failed sign-ins with a user name no account has.
Platform admins choose which log they read with Audit log of, before the search box: the selected company, or Platform (no company). The platform's log offers its own actions (Update settings) and resource (Settings) in the filters; the report export needs a company. Company admins and auditors read their company's log only. API: scope=platform (platform admins only; others get 403).
How long entries are kept
A company's entries are kept as long as its Keep audit log entries for (days) setting says (365 days unless the company sets 30 to 3,650; see Governance tab); the platform's own entries 365 days. Older entries are removed about once an hour.
Export report
Export report downloads the company's compliance report for a period. Platform admins, company admins and auditors can export it; a company must be selected.
| Setting (label in the UI) | What it does | Default | Allowed values |
|---|---|---|---|
| From, To | The period, as days in the company's time zone. The end day is included | The last 30 days (or the dates of the From date / To date filters, when set) | Any dates |
| Changes | Which merge requests the report covers. Merged in the period: merge requests merged between the two dates. Opened in the period: merge requests opened between the two dates | Merged in the period | Merged in the period, Opened in the period |
| Format | CSV or PDF | CSV | CSV, PDF |
The report holds the merge requests of the period, the company's audit entries of the period, and direct changes. Each part has a limit:
| Format | Merge requests | Audit entries |
|---|---|---|
| CSV | 10,000 | 10,000 |
| 2,000 | 5,000 |
When a part is cut at its limit, the page says Report truncated and, for each part cut (merge requests, audit entries, changes outside change management), how many of its records are included. Use a shorter period for complete data.
Each export is itself recorded as a compliance_export entry.
Audit actions
Merge Pilot writes more than 200 different actions. They are listed below by area.
- Who: person means the entry names the person who acted; Merge Pilot means Merge Pilot acted by itself (user
merge-pilot). - Platform: the entry belongs to no company (see Which company's entries are shown).
- Most actions are written only on success. Where an action can also be written with status
failure, the table says so.
Sign-in and sessions
See Sign-in.
| Action | When it is written | Who |
|---|---|---|
login | Someone signed in with a Merge Pilot password or with the company directory (LDAP). Failure, with the reason, when the user name or password was wrong, when the address is locked out of the user name, or when the account is slowed down after failed sign-ins. A failure goes to the log of the company of the account with that user name (or of the company the person signed in to), else the platform's | person |
login_locked | Failure only: an address was locked out of a user name after 10 failed sign-ins within 15 minutes, or the number the company's password policy sets (see Sign-in) | person |
break_glass_login | A platform admin signed in with a password while password sign-in is turned off on the platform. Platform | person |
ldap_login | Failure only: the directory accepted the password, but the person is in none of the groups allowed to sign in (details: their groups); or the directory could not check the sign-in (it could not be reached, refused Merge Pilot's bind user, or its search failed; details: the reason) | person |
oauth_callback | GitLab or GitHub sent someone back after sign-in. Failure when no Merge Pilot account is linked to that VCS account, when the email domain is not allowed, or when the account is deactivated | person |
oauth_login | The Merge Pilot session was created after a GitLab or GitHub sign-in | person |
sso_login | Someone signed in through an identity provider (OIDC or SAML). Also written with failure when the sign-in is refused | person |
session_refused | Failure only: a session could not be renewed because the way the person signed in no longer lets them in (the method was turned off, or the directory or identity provider withdrew them) | person |
logout | Someone signed out | person |
logout_everywhere | Someone signed out of all their sessions | person |
Own account
| Action | When it is written | Who |
|---|---|---|
change_own_password | Someone changed their own password. Failure when the current password was wrong | person |
update_profile | Someone changed their own profile | person |
vcs_account_linked | Someone linked their GitLab or GitHub account | person |
vcs_account_unlinked | Someone unlinked their GitLab or GitHub account | person |
sso_account_linked | An existing account was linked to an identity provider at sign-in | person |
sso_account_unlinked | An account was unlinked from an identity provider | person |
sso_identity_linked | An account was linked to an identity provider at its first sign-in with it, through a company admin's invitation (details: provider, by: invitation) | person |
sso_role_changed | At sign-in, the identity provider's groups gave the person a different role | person |
ldap_role_changed | At sign-in, the company directory's groups gave the person a different role | person |
project_renamed | A repository was renamed or moved on the VCS; Merge Pilot took over its new path | Merge Pilot |
sso_link_invited | A company admin invited a person to link an identity provider account at their next sign-in | The admin |
sso_link_invite_withdrawn | A company admin withdrew such an invitation | The admin |
mr_fetch_requested | Someone asked Merge Pilot to process a merge request by its number | The person |
mr_deleted_on_vcs | A merge request was deleted on the VCS: it was closed in Merge Pilot and its undecided change approval cancelled | Merge Pilot |
vcs_access_lost | Merge Pilot no longer reaches a repository (the GitHub App lost it, or the VCS answers 404 or 403 for it) | Merge Pilot |
open_mr_sweep_capped | A repository has more open merge requests than one check for missed merge requests looks at (2,000): the rest are found by their webhooks only | Merge Pilot |
project_forgotten | A company admin took a repository out of Merge Pilot without touching the VCS, with the reason and what was left there | The admin |
change_approval_assignee_deactivated | A change approval's assignee was deactivated: it was assigned again, or kept with a warning | The admin |
tracker_account_learned | Merge Pilot found a person's tracker account by their email and stored it | Merge Pilot |
notification_preferences_changed | Someone turned personal notification emails on or off in My profile (details: the events and their new state) | person |
notification_unsubscribed | Someone turned a personal notification email off with its unsubscribe link (details: the event, and one_click when a mail program's one-click button did it) | person |
Users
See Roles and users.
These entries go to the log of the user's company (a platform admin's: the platform's).
| Action | When it is written | Who |
|---|---|---|
create_user | A user was created | person |
update_user | A user was changed. A user moved to another company is recorded in the logs of both companies | person |
deactivate_user | A user was deactivated; their sessions end | person |
change_password | A user's password was set by an admin. When it was set for someone else, that person must change it at the next sign-in | person |
Platform settings and license
See Platform settings.
| Action | When it is written | Who |
|---|---|---|
update_settings | The platform settings were saved, with what changed. Failure when saving failed. Platform | person |
security_config | Merge Pilot started. Records the security safeguards, rate limits and job settings in effect, and the version. Platform | Merge Pilot |
set_license_api_key | The license API key was set. Can be a failure. Platform | person |
activate_license | A license was activated, online or offline. Can be a failure. Platform | person |
deactivate_license | The license was deactivated. Can be a failure. Platform | person |
check_license | A platform admin checked the license with Check now. A failure when the check failed or the license is not valid. Platform | person |
Companies
| Action | When it is written | Who |
|---|---|---|
create_company | A company was created | person |
update_company | A company's settings were changed, with what changed. Also written when a reviewed change is approved and applied (the entry names the approver). Can be a failure | person |
smtp_test_sent | Someone sent a test email with Send test email (details: the mail server and, for a failure, why). Success or failure | person |
delete_company | A company was deleted (deactivated). Can be a failure. Deactivating a company, this way or with active: false on update, releases the access its people got through Merge Pilot and the tokens it created: vcs_access_grants_released and vcs_issued_tokens_released with reason company_deactivated follow | person |
Reviewed control changes
When a company reviews control changes, a change waits for a second person.
| Action | When it is written | Who |
|---|---|---|
config_change_requested | A change to company settings, the company directory, identity providers, change policies, approver pools or vulnerability exceptions was sent for review | person |
config_change_approved | A second person approved a waiting change | person |
config_change_rejected | A second person rejected a waiting change | person |
Identity providers
See Identity providers.
| Action | When it is written | Who |
|---|---|---|
identity_provider_created | An OIDC or SAML identity provider was added | person |
identity_provider_updated | An identity provider was changed (or a reviewed change to it was approved) | person |
identity_provider_deleted | An identity provider was deleted (or a reviewed deletion was approved) | person |
API tokens
See API tokens.
| Action | When it is written | Who |
|---|---|---|
api_token_created | An API token was created | person |
api_token_revoked | An API token was revoked | person |
Connections
| Action | When it is written | Who |
|---|---|---|
create_connection | A VCS or tracker connection was created | person |
update_connection | A connection was changed, with what changed | person |
delete_connection | A connection was deleted | person |
update_tracker_settings | A tracker connection's settings were changed | person |
update_vcs_settings | A VCS connection's settings were changed | person |
update_vcs_permissions | A VCS connection's permissions were changed | person |
link_tracker | A tracker connection was linked to a VCS connection, or unlinked | person |
update_vcs_usage | A VCS connection's usage settings (tracker link, approver settings and permissions) were saved together | person |
github_app_registration_started | Registering a GitHub App for a connection was started | person |
github_app_registered | GitHub finished registering the App | Merge Pilot |
github_app_installations_synced | The GitHub App's installations were read again, on request or because GitHub reported a change | person or Merge Pilot |
github_app_removed | The GitHub App was removed from a connection | person |
connection_unhealthy | A connection got a problem: its credentials refused, GitHub App permissions missing, its API rate limit used up, or it was turned off (details: problem, provider). Once per change; also sent as the Connection problem notification (see Connection health) | Merge Pilot |
connection_recovered | A connection's problem is gone (details: the problem it had). Also sent as Connection recovered | Merge Pilot |
Webhooks
| Action | When it is written | Who |
|---|---|---|
webhook_accepted | A merge request event from the VCS, or an event from the tracker, was accepted | Merge Pilot |
webhook_job_failed | An accepted VCS event could not be queued for processing | Merge Pilot |
webhook_refused | A webhook for a connection was refused because it did not carry the connection's webhook secret (at most one entry a minute per connection; the details name the connection, provider and the address it came from) | Merge Pilot |
notification_redelivered | Someone sent a notification delivery (a route's or a personal email) again | person |
notification_route_tested | Someone sent a test to a notification route (Send test; details: the delivery ID) | person |
notification_failed | A notification delivery failed for good (details: the route or the person, the channel, the event, the kind of failure, the delivery ID), or could not even be queued (kind of failure could not be queued, no delivery ID, not announced). Also announced as Notification not delivered to the other routes (see Delivery log and failures) | Merge Pilot |
notification_personal_skipped | Personal notification emails were not sent because the company has no mail server (at most once a day) | Merge Pilot |
Change policies and approver pools
| Action | When it is written | Who |
|---|---|---|
policy_created | A change policy was created | person |
policy_updated | A change policy was changed | person |
policy_deleted | A change policy was deleted | person |
policy_reordered | The order of the policies was changed | person |
policy_template_applied | A policy template was applied | person |
approver_pool_created | An approver pool was created | person |
approver_pool_updated | An approver pool was changed | person |
approver_pool_deleted | An approver pool was deleted | person |
When a company reviews control changes, these entries are written when the change is approved, and name the approver.
Projects
| Action | When it is written | Who |
|---|---|---|
cm_setup | A repository was put under change management (also per repository in a bulk operation, and by automatic watching when the company adds new repositories under change management, then as Merge Pilot with automatic in the details). Can be a failure | person, Merge Pilot |
cm_remove | A repository was taken out of change management. Can be a failure | person |
project_mode_changed | A project was switched between watching and change management (also per repository in a bulk operation). Can be a failure | person |
project_watched | A repository was watched by a bulk operation, or by automatic watching (as Merge Pilot, with automatic in the details). Can be a failure | person, Merge Pilot |
project_unwatched | A project stopped being watched (also per repository in a bulk operation). Can be a failure | person |
When a person asked for it, cm_setup and cm_remove, and the per-repository entries of a bulk operation, carry the same details as the VCS operations: who asked, the rule that allowed it and the role found on the repository, and that Merge Pilot's account did it.
| project_branches_updated | The branches of a project were changed | person |
| project_history_imported | Someone imported a watched project's history again | person |
| update_project_vcs_settings | A project's VCS settings were changed | person |
| update_project_push_ignore | A project's list of accounts whose direct changes are ignored was changed | person |
| update_project_sca_exclude | A project's paths left out of the dependency scan were changed | person |
| update_tracker_override | A project's tracker setting was changed | person |
| analysis_triggered | A company admin started a project analysis | person |
| project_analysis | A project analysis finished (dependencies, vulnerabilities, licenses) | Merge Pilot |
| vulnerability_inventory_cleared | The company settings were saved with the container image or infrastructure inventory off, and the findings it kept (open and fixed) were deleted (details: kind, findings, snapshots) | Merge Pilot |
| iac_findings_skipped_deleted | The company settings were saved with infrastructure checks left out (Checks left out), and the open infrastructure findings of those checks were deleted (details: findings, checks) | Merge Pilot |
| sbom_exported | Someone exported a project's SBOM | person |
Bulk operations
| Action | When it is written | Who |
|---|---|---|
bulk_operation_started | A bulk operation started | person |
bulk_operation_finished | A bulk operation finished | person |
bulk_operation_cancelled | A bulk operation ended because it was cancelled | person |
bulk_operation_cancel_requested | Someone asked to cancel a bulk operation | person |
Bulk operation entries name the person who started the operation.
Direct changes and branch protection
| Action | When it is written | Who |
|---|---|---|
direct_change | A change reached a watched branch without a merge request | Merge Pilot |
direct_change_ignored | Such a change was made by an ignored account | Merge Pilot |
direct_change_violation | Such a change reached a branch under change management | Merge Pilot |
protection_weakened | A project's branch protection lets changes skip change management | Merge Pilot |
protection_restored | A project's branch protection no longer lets changes skip change management | Merge Pilot |
Merge request evaluation
| Action | When it is written | Who |
|---|---|---|
mr_policy_matched | A merge request was matched to a change policy | Merge Pilot |
mr_gate_approved | The merge gate opened for the merge request's current commit | Merge Pilot |
mr_gate_pending | The merge gate is waiting (a control has not passed yet) | Merge Pilot |
mr_gate_blocked | The merge gate is blocked | Merge Pilot |
mr_watched_approved | In a watched repository: the gate would be open (nothing was written to the VCS) | Merge Pilot |
mr_watched_pending | In a watched repository: the gate would be waiting | Merge Pilot |
mr_watched_blocked | In a watched repository: the gate would be blocked | Merge Pilot |
mr_rejected | A merge request was closed by its policy. Details: the policy, its version, the reason and the head commit (head_sha) | Merge Pilot |
mr_validated | The merge request's work items were validated | Merge Pilot |
mr_risk_blocked | The risk assessment blocked the merge request | Merge Pilot |
mr_approvers_short | Too few people may approve the change for the approval the policy asks | Merge Pilot |
mr_out_of_scope | A merge request now targets a branch change management does not cover | Merge Pilot |
emergency_declared | A merge request was declared an emergency change | Merge Pilot |
emergency_review_overdue | The review of an emergency change is overdue | Merge Pilot |
merge_group_checked | A merge queue group was checked for the change approval check | Merge Pilot |
The mr_gate_* and mr_watched_* entries record a decision, not every evaluation: one is written when the merge request gets a new head commit, a new target branch or a different gate outcome, when the repository moves between watched and change management, and again when the previous attempt to set the merge gate failed. A control that only settles without changing the outcome (for example a scan finishing while another control still holds the gate) writes no new entry; the merge gate on the VCS still shows the latest state of every control. Their details hold the policy, its version, the head commit (head_sha) and the controls; mr_watched_* also whether a change approval would be needed.
The messages of these entries, and of mr_rejected and the scan entries below, name the merge request (on GitHub: pull request) with its head commit, for example PR #165 @ed3d7f9, so the decisions on two commits of the same change read apart.
Scans
| Action | When it is written | Who |
|---|---|---|
secrets_detected | The secret scan found potential secrets in a merge request; written again when the findings differ from the previous scan's | Merge Pilot |
secrets_allowed_inline | Findings were marked gitleaks:allow by the author; written again when they differ from the previous scan's | Merge Pilot |
sca_scan | The dependency scan of a merge request finished with a result that differs from the previous scan's (status, new vulnerabilities, highest severity, license or package findings) | Merge Pilot |
dependency_sources_detected | The dependency source check found findings in a merge request (informational ones included); written again when their number changes. Details: the repository, the merge request number, the head commit, the findings that fail the check, the informational ones, the count per rule and the files checked | Merge Pilot |
workflow_problems_detected | The CI configuration check found problems in the changed CI configuration (GitHub Actions workflows or GitLab CI configuration); written again when their number changes. Details: the repository, the merge request number, the head commit, the number of findings and the files checked | Merge Pilot |
secret_rescan | Someone started the secret scan of a merge request again | person |
sca_rescan | Someone started the dependency scan of a merge request again | person |
workflow_rescan | Someone started the CI configuration check of a merge request again | person |
image_vulnerabilities_detected | The container image scan found vulnerabilities in the images a merge request starts referring to | Merge Pilot |
image_rescan | Someone started the container image scan of a merge request again | person |
iac_problems_detected | The infrastructure check found misconfigurations a merge request introduces | Merge Pilot |
iac_rescan | Someone started the infrastructure check of a merge request again | person |
registry_test | A company admin tested a container registry sign-in. Can be a failure | person |
The details of every scan entry above, except the re-scans, carry the head commit that was scanned (head_sha).
Merges
| Action | When it is written | Who |
|---|---|---|
mr_merged | A merge request was merged | Merge Pilot |
mr_merged_through_other | A merge request counts as merged because its commits reached the target branch another way | Merge Pilot |
mr_merged_would_have_blocked | In a watched repository, a merge request was merged that change management would have held | Merge Pilot |
mr_merged_without_approval | A merge request was merged without change-management approval | Merge Pilot |
mr_merged_in_freeze | A merge request was merged during a change freeze | Merge Pilot |
mr_sod_flag | Someone approved the change and merged it, and the policy flags this | Merge Pilot |
mr_sod_block | Someone approved the change and merged it, and the policy forbids this | Merge Pilot |
sod_flag_failed | Failure only: a separation-of-duties exception of a vote or take-over could not be stored on the merge request; this entry keeps it instead (details: the flag) | person |
Change approvals
| Action | When it is written | Who |
|---|---|---|
change_approval_created | A change approval was opened in the tracker | Merge Pilot |
change_approval_cancelled | A change approval was cancelled: the merge request closed without merging or left change management | Merge Pilot |
change_approval_assigned | A change approval was assigned once someone could take it | Merge Pilot |
change_approval_assign_me | Someone took a change approval. Can be a failure | person |
change_approval_taken_over | Someone took over a change approval assigned to another person. Can be a failure | person |
change_approval_reassigned_in_tracker | Someone reassigned or unassigned a change approval in Jira; Merge Pilot follows it (details: from, to, who) | Merge Pilot |
change_approval_vote | An approving or rejecting vote was counted | person or Merge Pilot |
change_approval_vote_ineligible | A vote was ignored because the voter may not decide this change | Merge Pilot |
change_approval_self_approval_blocked | The merge request author's approval was ignored | Merge Pilot |
mr_approved | A change approval was approved | Merge Pilot |
change_approval_rejected | A change approval was rejected | Merge Pilot |
change_approval_rejection_withdrawn | A rejection was withdrawn, by its rejecter or a company administrator | person |
change_approval_decided_after_mr_merged | A change approval was decided after its merge request was merged | Merge Pilot |
change_approval_decided_after_mr_closed | A change approval was decided after its merge request was closed | Merge Pilot |
change_approval_superseded | A change approval was replaced by a new one | Merge Pilot |
change_approval_reopened | A change approval was reopened | Merge Pilot |
change_approval_new_commits_kept | A change approval was kept although new commits arrived, as the policy allows | Merge Pilot |
change_approval_quorum_met_on_policy_change | Under the current policy and risk level, the approvals already given were enough | Merge Pilot |
change_approval_lost | A change approval is no longer valid | Merge Pilot |
change_approval_approval_revoked | An approval was revoked; the merge request waits for approval again | Merge Pilot |
change_approval_approval_revoked_after_merge | An approval was revoked after the merge request was merged | Merge Pilot |
change_approval_sync_failed | Failure only: moving the change approval in the tracker failed | Merge Pilot |
change_approval_decided_by_admin | An admin moved a change approval they were not assigned to. Only possible when the installation allows admins to decide any change approval | person |
approval_fatigue_detected | One approver approved many change approvals in a short time | person or Merge Pilot |
change_approval_due_soon | A change approval's deadline (or an emergency change's review deadline) is near: a quarter of its time left, at most a day (details: the key, the deadline, whether it is an emergency) | Merge Pilot |
change_approval_overdue | A normal change's change approval passed its deadline undecided (see Change approval deadline) | Merge Pilot |
Actions on merge requests
| Action | When it is written | Who |
|---|---|---|
risk_allow | Someone accepted a merge request's risk | person |
freeze_release | Someone let a held change go ahead during a change freeze | person |
work_item_usage_reset | An admin restarted the usage count of a work item | person |
mr_resync | Someone asked Merge Pilot to resync a merge request | person |
Delegations and vulnerability exceptions
| Action | When it is written | Who |
|---|---|---|
delegation_created | An approver handed over their votes to someone else | person |
delegation_deleted | A delegation was removed | person |
vuln_exception_created | A vulnerability exception was created (or a reviewed one was approved) | person |
vuln_exception_revoked | A vulnerability exception was revoked (or a reviewed revocation was approved) | person |
vuln_exception_expired | A vulnerability exception expired | Merge Pilot |
Built-in tracker
| Action | When it is written | Who |
|---|---|---|
tracker_project_created | A tracker project was created | person |
tracker_project_updated | A tracker project was changed | person |
tracker_project_archived | A tracker project was archived | person |
tracker_issue_created | An issue was created | Merge Pilot |
tracker_issue_updated | An issue was changed | Merge Pilot |
tracker_issue_transitioned | An issue moved to another state | person or Merge Pilot |
tracker_issue_assigned | An issue was assigned | person or Merge Pilot |
Entries for issues created or changed record the person's name in the entry's message.
VCS operations
Operations on GitLab or GitHub done through Merge Pilot. Each can also be written with status failure. The details of each entry say:
requested_by: who asked;rule: what allowed it, eithercompany adminor the connection's rule (its operation, Merge Pilot roles and minimum role on the repository);vcs_access_level: the role the person's own account had on the repository (for a group: on one of the company's repositories in it, named byaccess_via_project_id, or on the group itself, without it). It is left out where no role was read: for company admins (ruleis thencompany admin), for joining and leaving (no minimum role), and for a token revoked by the person who asked for it (allowed_as:requester, norule);allowed_as:memberwhen someone left a project or group the rule for joining would no longer let them join (leaving needs no rule),requesterfor a token revoked by the person who asked for it;acted_as:merge-pilot, because Merge Pilot's own account did the operation;refused: for a refusal Merge Pilot made itself, the reason (for example a branch under change management, or a group holding repositories that are not the company's).
| Action | When it is written | Who |
|---|---|---|
vcs_join_project | Someone joined a project | person |
vcs_leave_project | Someone left a project | person |
vcs_access_grant_dropped | The access someone got by joining is no longer on the VCS, so Merge Pilot stopped tracking it, with the reason: on GitHub no access and no invitation any more (taken back, declined or expired there); on GitLab no direct membership of the project, or no membership of the group, any more. With project_id or group_id | person (whose membership was read) |
vcs_access_grants_released | Access people got by joining through Merge Pilot was released, with the reason: the person left the company or lost their place in it (deactivated, moved_to_another_company, made_platform_admin), unlinked their VCS account (unlinked), the repository was removed from Merge Pilot (project_removed), the connection was deleted (connection_deleted, with connection_name) or the company was deactivated (company_deactivated); with the count and the list (kind: project with the repository, or group with group_id and group_path; the connection, VCS user name and role). sweep: true when Merge Pilot released it on a later try, after the first one failed. A failure with the error when it could not be released. The access stays on the VCS; company admins see it under People and are told by the VCS access to review notification | person, Merge Pilot |
vcs_access_grant_dismissed | A company admin dismissed a released access record (with its kind, the repository or the group's group_id and group_path, the person, their VCS account, the role and why it was released) | person |
vcs_join_group | Someone joined a group, with its group_path. A failure with refused when a project of the group or its subgroups is not the company's in Merge Pilot, or (for anyone but a company admin) when the group is shared with other groups | person |
vcs_leave_group | Someone left a group, with its group_path | person |
vcs_create_project_var | A project variable or secret was created, with its environment (GitLab: environment scope) and options (variable_type, raw, hidden on GitLab); never its value | person |
vcs_update_project_var | A project variable or secret was changed, with its environment (GitLab: environment scope) and the options changed; never its value | person |
vcs_delete_project_var | A project variable or secret was deleted | person |
vcs_create_group_var | A group (GitHub: organization) variable or secret was created; on GitHub with the number of repositories it was given to. On GitLab a failure with refused when a project of the group or its subgroups is not the company's in Merge Pilot | person |
vcs_update_group_var | A group (GitHub: organization) variable or secret was changed; never its value. A failure with refused when other teams' repositories can use it too | person |
vcs_delete_group_var | A group variable or secret was deleted | person |
vcs_protect_branch | A branch was protected (GitHub: its Merge Pilot protected: <branch> ruleset was created). With cm_gated when it covers a branch under change management: on GitLab, protecting with a pattern that can cover such a branch is a failure with refused for anyone but a company admin | person |
vcs_unprotect_branch | A branch's protection was removed. With cm_gated when the branch is under change management: a failure with refused for anyone but a company admin; on GitLab, for an admin, with the warning that change management's approval rule is no longer linked to the branch | person |
vcs_toggle_force_push | Force push on a branch was turned on or off; on GitHub with the warning when another ruleset still blocks it. With cm_gated when the branch is under change management: a failure with refused for anyone but a company admin | person |
vcs_create_access_token | A GitLab project access token was created, with its name, scopes, access_level, expires_at and GitLab's vcs_token_id; never its value | person |
vcs_create_deploy_token | A GitLab deploy token was created, with its name, scopes, expires_at, username when given, and GitLab's vcs_token_id; never its value | person |
vcs_revoke_token | A token Merge Pilot created was revoked, with its kind, name, scopes and expiry, and who asked for it (token_requested_by). allowed_as: requester when the person who asked for it revoked it; a warning when GitLab no longer had it | person |
vcs_issued_tokens_released | Tokens Merge Pilot created were released, with the reason: the person who asked for them left the company, the repository was removed from Merge Pilot (project_removed), the connection was deleted or the company was deactivated (company_deactivated); with the list: kind, name, repository, scopes, role and expiry. sweep: true when released on a later try | person, Merge Pilot |
vcs_issued_token_dismissed | A company admin dismissed a released token's record | person |
Reports and jobs
| Action | When it is written | Who |
|---|---|---|
compliance_export | Someone exported the compliance report. Failure when the export failed | person |
job_failed | A background job failed after its retries (see Jobs). Details: the job ID, its type, the error and, for a merge request's job, the repository, the merge request number and, when the job names one, the head commit (head_sha) it worked on | Merge Pilot |
job_retried | An admin queued a failed or retrying job again, with its job ID, type and attempt | person |
Related pages
Video tutorial
Short videos of this feature working on real GitLab and Jira projects. English audio, English and Turkish subtitles. All video tutorials →