Skip to main content
Video tutorial · 0:54

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​

RoleAudit log
Platform adminEvery company's entries, and the platform's log
Company adminTheir own company's entries
AuditorTheir own company's entries
Policy managerNo access
UserNo 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 showsAPI field
TimeWhen the entry was written, shown as a relative timecreated_at
UserThe person who acted. Actions Merge Pilot takes by itself show merge-pilotusername
ActionThe action name, for example policy_updated (see Audit actions)action
ResourceThe kind of object acted on, for example merge_request, policy, userresource
Resource IDThe ID of that objectresource_id
Statussuccess or failurestatus
IPThe 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 fromip

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 doesAPI parameter
Search username or actionFinds entries whose user name or action contains the text, ignoring caseq
ActionOne action. The list offers All actions and a selection of common actions; to find any other action, type its name in the search boxaction
StatusAll statuses, Success or Failurestatus
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 policyresource
Username (under More filters)The exact user nameusername
IP address (under More filters)The exact IPip
From date, To date (under More filters)Only entries from this day, and up to the end of this dayfrom, 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 doesDefaultAllowed values
From, ToThe period, as days in the company's time zone. The end day is includedThe last 30 days (or the dates of the From date / To date filters, when set)Any dates
ChangesWhich 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 datesMerged in the periodMerged in the period, Opened in the period
FormatCSV or PDFCSVCSV, 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:

FormatMerge requestsAudit entries
CSV10,00010,000
PDF2,0005,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.

ActionWhen it is writtenWho
loginSomeone 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'sperson
login_lockedFailure 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_loginA platform admin signed in with a password while password sign-in is turned off on the platform. Platformperson
ldap_loginFailure 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_callbackGitLab 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 deactivatedperson
oauth_loginThe Merge Pilot session was created after a GitLab or GitHub sign-inperson
sso_loginSomeone signed in through an identity provider (OIDC or SAML). Also written with failure when the sign-in is refusedperson
session_refusedFailure 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
logoutSomeone signed outperson
logout_everywhereSomeone signed out of all their sessionsperson

Own account​

ActionWhen it is writtenWho
change_own_passwordSomeone changed their own password. Failure when the current password was wrongperson
update_profileSomeone changed their own profileperson
vcs_account_linkedSomeone linked their GitLab or GitHub accountperson
vcs_account_unlinkedSomeone unlinked their GitLab or GitHub accountperson
sso_account_linkedAn existing account was linked to an identity provider at sign-inperson
sso_account_unlinkedAn account was unlinked from an identity providerperson
sso_identity_linkedAn 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_changedAt sign-in, the identity provider's groups gave the person a different roleperson
ldap_role_changedAt sign-in, the company directory's groups gave the person a different roleperson
project_renamedA repository was renamed or moved on the VCS; Merge Pilot took over its new pathMerge Pilot
sso_link_invitedA company admin invited a person to link an identity provider account at their next sign-inThe admin
sso_link_invite_withdrawnA company admin withdrew such an invitationThe admin
mr_fetch_requestedSomeone asked Merge Pilot to process a merge request by its numberThe person
mr_deleted_on_vcsA merge request was deleted on the VCS: it was closed in Merge Pilot and its undecided change approval cancelledMerge Pilot
vcs_access_lostMerge 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_cappedA repository has more open merge requests than one check for missed merge requests looks at (2,000): the rest are found by their webhooks onlyMerge Pilot
project_forgottenA company admin took a repository out of Merge Pilot without touching the VCS, with the reason and what was left thereThe admin
change_approval_assignee_deactivatedA change approval's assignee was deactivated: it was assigned again, or kept with a warningThe admin
tracker_account_learnedMerge Pilot found a person's tracker account by their email and stored itMerge Pilot
notification_preferences_changedSomeone turned personal notification emails on or off in My profile (details: the events and their new state)person
notification_unsubscribedSomeone 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).

ActionWhen it is writtenWho
create_userA user was createdperson
update_userA user was changed. A user moved to another company is recorded in the logs of both companiesperson
deactivate_userA user was deactivated; their sessions endperson
change_passwordA user's password was set by an admin. When it was set for someone else, that person must change it at the next sign-inperson

Platform settings and license​

See Platform settings.

ActionWhen it is writtenWho
update_settingsThe platform settings were saved, with what changed. Failure when saving failed. Platformperson
security_configMerge Pilot started. Records the security safeguards, rate limits and job settings in effect, and the version. PlatformMerge Pilot
set_license_api_keyThe license API key was set. Can be a failure. Platformperson
activate_licenseA license was activated, online or offline. Can be a failure. Platformperson
deactivate_licenseThe license was deactivated. Can be a failure. Platformperson
check_licenseA platform admin checked the license with Check now. A failure when the check failed or the license is not valid. Platformperson

Companies​

ActionWhen it is writtenWho
create_companyA company was createdperson
update_companyA 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 failureperson
smtp_test_sentSomeone sent a test email with Send test email (details: the mail server and, for a failure, why). Success or failureperson
delete_companyA 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 followperson

Reviewed control changes​

When a company reviews control changes, a change waits for a second person.

ActionWhen it is writtenWho
config_change_requestedA change to company settings, the company directory, identity providers, change policies, approver pools or vulnerability exceptions was sent for reviewperson
config_change_approvedA second person approved a waiting changeperson
config_change_rejectedA second person rejected a waiting changeperson

Identity providers​

See Identity providers.

ActionWhen it is writtenWho
identity_provider_createdAn OIDC or SAML identity provider was addedperson
identity_provider_updatedAn identity provider was changed (or a reviewed change to it was approved)person
identity_provider_deletedAn identity provider was deleted (or a reviewed deletion was approved)person

API tokens​

See API tokens.

ActionWhen it is writtenWho
api_token_createdAn API token was createdperson
api_token_revokedAn API token was revokedperson

Connections​

ActionWhen it is writtenWho
create_connectionA VCS or tracker connection was createdperson
update_connectionA connection was changed, with what changedperson
delete_connectionA connection was deletedperson
update_tracker_settingsA tracker connection's settings were changedperson
update_vcs_settingsA VCS connection's settings were changedperson
update_vcs_permissionsA VCS connection's permissions were changedperson
link_trackerA tracker connection was linked to a VCS connection, or unlinkedperson
update_vcs_usageA VCS connection's usage settings (tracker link, approver settings and permissions) were saved togetherperson
github_app_registration_startedRegistering a GitHub App for a connection was startedperson
github_app_registeredGitHub finished registering the AppMerge Pilot
github_app_installations_syncedThe GitHub App's installations were read again, on request or because GitHub reported a changeperson or Merge Pilot
github_app_removedThe GitHub App was removed from a connectionperson
connection_unhealthyA 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_recoveredA connection's problem is gone (details: the problem it had). Also sent as Connection recoveredMerge Pilot

Webhooks​

ActionWhen it is writtenWho
webhook_acceptedA merge request event from the VCS, or an event from the tracker, was acceptedMerge Pilot
webhook_job_failedAn accepted VCS event could not be queued for processingMerge Pilot
webhook_refusedA 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_redeliveredSomeone sent a notification delivery (a route's or a personal email) againperson
notification_route_testedSomeone sent a test to a notification route (Send test; details: the delivery ID)person
notification_failedA 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_skippedPersonal notification emails were not sent because the company has no mail server (at most once a day)Merge Pilot

Change policies and approver pools​

ActionWhen it is writtenWho
policy_createdA change policy was createdperson
policy_updatedA change policy was changedperson
policy_deletedA change policy was deletedperson
policy_reorderedThe order of the policies was changedperson
policy_template_appliedA policy template was appliedperson
approver_pool_createdAn approver pool was createdperson
approver_pool_updatedAn approver pool was changedperson
approver_pool_deletedAn approver pool was deletedperson

When a company reviews control changes, these entries are written when the change is approved, and name the approver.

Projects​

ActionWhen it is writtenWho
cm_setupA 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 failureperson, Merge Pilot
cm_removeA repository was taken out of change management. Can be a failureperson
project_mode_changedA project was switched between watching and change management (also per repository in a bulk operation). Can be a failureperson
project_watchedA repository was watched by a bulk operation, or by automatic watching (as Merge Pilot, with automatic in the details). Can be a failureperson, Merge Pilot
project_unwatchedA project stopped being watched (also per repository in a bulk operation). Can be a failureperson

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​

ActionWhen it is writtenWho
bulk_operation_startedA bulk operation startedperson
bulk_operation_finishedA bulk operation finishedperson
bulk_operation_cancelledA bulk operation ended because it was cancelledperson
bulk_operation_cancel_requestedSomeone asked to cancel a bulk operationperson

Bulk operation entries name the person who started the operation.

Direct changes and branch protection​

ActionWhen it is writtenWho
direct_changeA change reached a watched branch without a merge requestMerge Pilot
direct_change_ignoredSuch a change was made by an ignored accountMerge Pilot
direct_change_violationSuch a change reached a branch under change managementMerge Pilot
protection_weakenedA project's branch protection lets changes skip change managementMerge Pilot
protection_restoredA project's branch protection no longer lets changes skip change managementMerge Pilot

Merge request evaluation​

ActionWhen it is writtenWho
mr_policy_matchedA merge request was matched to a change policyMerge Pilot
mr_gate_approvedThe merge gate opened for the merge request's current commitMerge Pilot
mr_gate_pendingThe merge gate is waiting (a control has not passed yet)Merge Pilot
mr_gate_blockedThe merge gate is blockedMerge Pilot
mr_watched_approvedIn a watched repository: the gate would be open (nothing was written to the VCS)Merge Pilot
mr_watched_pendingIn a watched repository: the gate would be waitingMerge Pilot
mr_watched_blockedIn a watched repository: the gate would be blockedMerge Pilot
mr_rejectedA merge request was closed by its policy. Details: the policy, its version, the reason and the head commit (head_sha)Merge Pilot
mr_validatedThe merge request's work items were validatedMerge Pilot
mr_risk_blockedThe risk assessment blocked the merge requestMerge Pilot
mr_approvers_shortToo few people may approve the change for the approval the policy asksMerge Pilot
mr_out_of_scopeA merge request now targets a branch change management does not coverMerge Pilot
emergency_declaredA merge request was declared an emergency changeMerge Pilot
emergency_review_overdueThe review of an emergency change is overdueMerge Pilot
merge_group_checkedA merge queue group was checked for the change approval checkMerge 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​

ActionWhen it is writtenWho
secrets_detectedThe secret scan found potential secrets in a merge request; written again when the findings differ from the previous scan'sMerge Pilot
secrets_allowed_inlineFindings were marked gitleaks:allow by the author; written again when they differ from the previous scan'sMerge Pilot
sca_scanThe 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_detectedThe 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 checkedMerge Pilot
workflow_problems_detectedThe 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 checkedMerge Pilot
secret_rescanSomeone started the secret scan of a merge request againperson
sca_rescanSomeone started the dependency scan of a merge request againperson
workflow_rescanSomeone started the CI configuration check of a merge request againperson
image_vulnerabilities_detectedThe container image scan found vulnerabilities in the images a merge request starts referring toMerge Pilot
image_rescanSomeone started the container image scan of a merge request againperson
iac_problems_detectedThe infrastructure check found misconfigurations a merge request introducesMerge Pilot
iac_rescanSomeone started the infrastructure check of a merge request againperson
registry_testA company admin tested a container registry sign-in. Can be a failureperson

The details of every scan entry above, except the re-scans, carry the head commit that was scanned (head_sha).

Merges​

ActionWhen it is writtenWho
mr_mergedA merge request was mergedMerge Pilot
mr_merged_through_otherA merge request counts as merged because its commits reached the target branch another wayMerge Pilot
mr_merged_would_have_blockedIn a watched repository, a merge request was merged that change management would have heldMerge Pilot
mr_merged_without_approvalA merge request was merged without change-management approvalMerge Pilot
mr_merged_in_freezeA merge request was merged during a change freezeMerge Pilot
mr_sod_flagSomeone approved the change and merged it, and the policy flags thisMerge Pilot
mr_sod_blockSomeone approved the change and merged it, and the policy forbids thisMerge Pilot
sod_flag_failedFailure 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​

ActionWhen it is writtenWho
change_approval_createdA change approval was opened in the trackerMerge Pilot
change_approval_cancelledA change approval was cancelled: the merge request closed without merging or left change managementMerge Pilot
change_approval_assignedA change approval was assigned once someone could take itMerge Pilot
change_approval_assign_meSomeone took a change approval. Can be a failureperson
change_approval_taken_overSomeone took over a change approval assigned to another person. Can be a failureperson
change_approval_reassigned_in_trackerSomeone reassigned or unassigned a change approval in Jira; Merge Pilot follows it (details: from, to, who)Merge Pilot
change_approval_voteAn approving or rejecting vote was countedperson or Merge Pilot
change_approval_vote_ineligibleA vote was ignored because the voter may not decide this changeMerge Pilot
change_approval_self_approval_blockedThe merge request author's approval was ignoredMerge Pilot
mr_approvedA change approval was approvedMerge Pilot
change_approval_rejectedA change approval was rejectedMerge Pilot
change_approval_rejection_withdrawnA rejection was withdrawn, by its rejecter or a company administratorperson
change_approval_decided_after_mr_mergedA change approval was decided after its merge request was mergedMerge Pilot
change_approval_decided_after_mr_closedA change approval was decided after its merge request was closedMerge Pilot
change_approval_supersededA change approval was replaced by a new oneMerge Pilot
change_approval_reopenedA change approval was reopenedMerge Pilot
change_approval_new_commits_keptA change approval was kept although new commits arrived, as the policy allowsMerge Pilot
change_approval_quorum_met_on_policy_changeUnder the current policy and risk level, the approvals already given were enoughMerge Pilot
change_approval_lostA change approval is no longer validMerge Pilot
change_approval_approval_revokedAn approval was revoked; the merge request waits for approval againMerge Pilot
change_approval_approval_revoked_after_mergeAn approval was revoked after the merge request was mergedMerge Pilot
change_approval_sync_failedFailure only: moving the change approval in the tracker failedMerge Pilot
change_approval_decided_by_adminAn admin moved a change approval they were not assigned to. Only possible when the installation allows admins to decide any change approvalperson
approval_fatigue_detectedOne approver approved many change approvals in a short timeperson or Merge Pilot
change_approval_due_soonA 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_overdueA normal change's change approval passed its deadline undecided (see Change approval deadline)Merge Pilot

Actions on merge requests​

ActionWhen it is writtenWho
risk_allowSomeone accepted a merge request's riskperson
freeze_releaseSomeone let a held change go ahead during a change freezeperson
work_item_usage_resetAn admin restarted the usage count of a work itemperson
mr_resyncSomeone asked Merge Pilot to resync a merge requestperson

Delegations and vulnerability exceptions​

ActionWhen it is writtenWho
delegation_createdAn approver handed over their votes to someone elseperson
delegation_deletedA delegation was removedperson
vuln_exception_createdA vulnerability exception was created (or a reviewed one was approved)person
vuln_exception_revokedA vulnerability exception was revoked (or a reviewed revocation was approved)person
vuln_exception_expiredA vulnerability exception expiredMerge Pilot

Built-in tracker​

ActionWhen it is writtenWho
tracker_project_createdA tracker project was createdperson
tracker_project_updatedA tracker project was changedperson
tracker_project_archivedA tracker project was archivedperson
tracker_issue_createdAn issue was createdMerge Pilot
tracker_issue_updatedAn issue was changedMerge Pilot
tracker_issue_transitionedAn issue moved to another stateperson or Merge Pilot
tracker_issue_assignedAn issue was assignedperson 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, either company admin or 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 by access_via_project_id, or on the group itself, without it). It is left out where no role was read: for company admins (rule is then company admin), for joining and leaving (no minimum role), and for a token revoked by the person who asked for it (allowed_as: requester, no rule);
  • allowed_as: member when someone left a project or group the rule for joining would no longer let them join (leaving needs no rule), requester for 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).
ActionWhen it is writtenWho
vcs_join_projectSomeone joined a projectperson
vcs_leave_projectSomeone left a projectperson
vcs_access_grant_droppedThe 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_idperson (whose membership was read)
vcs_access_grants_releasedAccess 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 notificationperson, Merge Pilot
vcs_access_grant_dismissedA 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_groupSomeone 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 groupsperson
vcs_leave_groupSomeone left a group, with its group_pathperson
vcs_create_project_varA project variable or secret was created, with its environment (GitLab: environment scope) and options (variable_type, raw, hidden on GitLab); never its valueperson
vcs_update_project_varA project variable or secret was changed, with its environment (GitLab: environment scope) and the options changed; never its valueperson
vcs_delete_project_varA project variable or secret was deletedperson
vcs_create_group_varA 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 Pilotperson
vcs_update_group_varA group (GitHub: organization) variable or secret was changed; never its value. A failure with refused when other teams' repositories can use it tooperson
vcs_delete_group_varA group variable or secret was deletedperson
vcs_protect_branchA 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 adminperson
vcs_unprotect_branchA 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 branchperson
vcs_toggle_force_pushForce 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 adminperson
vcs_create_access_tokenA GitLab project access token was created, with its name, scopes, access_level, expires_at and GitLab's vcs_token_id; never its valueperson
vcs_create_deploy_tokenA GitLab deploy token was created, with its name, scopes, expires_at, username when given, and GitLab's vcs_token_id; never its valueperson
vcs_revoke_tokenA 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 itperson
vcs_issued_tokens_releasedTokens 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 tryperson, Merge Pilot
vcs_issued_token_dismissedA company admin dismissed a released token's recordperson

Reports and jobs​

ActionWhen it is writtenWho
compliance_exportSomeone exported the compliance report. Failure when the export failedperson
job_failedA 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 onMerge Pilot
job_retriedAn admin queued a failed or retrying job again, with its job ID, type and attemptperson

Video tutorial

Short videos of this feature working on real GitLab and Jira projects. English audio, English and Turkish subtitles. All video tutorials →

Audit Log and Compliance ReportYouTube ↗