Don't create audit events when there is no change
Release notes
Problem to solve
Right now audit events are created to whenever certain APIs are called. This is great for maintaining visibility whenever actions take place. However, it means that audit events are always created, even when no change has occurred. This can cause the audit log to be filled with events that aren't meaningful. See the screenshot below for an example where no actual changed occurred, yet an event was created.
Proposal
When an audit event is about to be created, check that there actually was a change. If there was, create the event if normal. However, if no change actually occurred, do not create an audit event.
Intended users
Feature Usage Metrics
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.