Comment on page
Merge Rules Audit Trail
It is important to know when your merge rules have been changed, and who changed them. We store a history of your merge rules configuration so that you can see exactly that.
For each of the ways that you may set up your merge rules, we store different relevant information. An overview of the differences can be found below.
A configuration history record of a change made via Dashboard UI
As can be seen above, the
aviator_useris displayed as the email associated with their Aviator account. The
diffitself is a simple text difference between the current and previous YAML displayed on the
Similarly to the above, when changes are made to Merge Rules YAML under the
Yaml Configurationtab, we store the
aviator_userthat logged in to make the change, the time, and the
diffof the current and previous YAML.
Since changes here are made directly to the YAML shown on the
Yaml Configurationtab, it should be more obvious how the text difference is generated in this case.
The configuration history record for dashboard YAML changes looks exactly the same as changes from the dashboard UI, so we won't repeat the example image.
Finally, when your YAML configuration file is set up in your repo, we store the
github_userwho pushed the changes onto your repo's default branch, the commit the change was made in, the time of the commit, and again the
diffbetween the updated config file and the previous one.
A configuration history record of a change made to the repository config YAML file
github_useris displayed as their GitHub
loginor username. The commit is represented as the short hash which links to the actual commit information.
While under this configuration set up, your source control also can act as its own audit trail. However, these changes are additionally stored in our database both for completeness and to make it clear what changes actually made it through in the event of any desync between
Aviatorand your source control.