File editor (Commit in browser) does not show up in audit log

Issue Summary

When using file editor in Bitbucket Server/Data Center, the audit log does not capture the Repository Written To even that it should since you are writing information to the repository.

Steps to Reproduce

1. Set Audit log for "End User Activity" to "Full" (or set audit.legacy.events.logging.forced=true in bitbucket.properties and "End User Activity" to "Base")
2. Ensure feature.file.editor in the bitbucket.properties file is not set to false.
3. Commit a change using the "Edit" feature on a file

Expected Results

Advanced and regular audit logs show "Repository written to" Event

Actual Results

"Repository written to" does not show up. The Push Log has the change and is labeled as "File edit"

Workaround

If you need to ensure the audit log has everything, set "feature.file.editor=false" in the bitbucket.properties file. This will disable the file editor feature.

Otherwise, the push log will have a record of the change.