Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,329
    • Merge requests 1,329
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #337993
Closed
Open
Issue created Aug 09, 2021 by Dan Jensen@djensenContributor6 of 6 checklist items completed6/6 checklist items

Audit Events: Deprecate and remove the `repository_push_audit_event` feature

Problem to solve

As described in #293031, the repository_push_audit_event feature effectively duplicated the existing "push" Event type while introducing a substantial performance problem and at least one bug.

Proposal

  • Deprecate the repository_push_audit_event feature in %14.3. See deprecation entry and docs update.
  • Clarify the docs in %14.8. See !79933 (merged)
  • Remove the repository_push_audit_event feature in %15.0.
  • Close dependent issues:
    • [Feature flag] Enable logging git push events by default on gitlab.com
    • RepositoryPushAuditEventWorker throws "ActiveRecord::StatementInvalid" exception if author has no current_sign_in_ip

Out of scope

  • Display push Event records in the project-level Audit Log
Edited May 02, 2022 by Harsimar Sandhu
Assignee
Assign to
Time tracking