Update audit_events.md by adding index.md at "Add it yourself"

Hey @mbroa04!

Thank you for your contribution to GitLab. Please refer to the contribution flow documentation for a quick overview of the process, and the merge request (MR) guidelines for the detailed process.

When you're ready for a first review, post @gitlab-bot ready. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with @gitlab-bot ready @user1 @user2.

At any time, if you need help moving the MR forward, feel free to post @gitlab-bot help. Read more on how to get help.

To enable automated checks on your MR, please configure Danger for your fork.

You can comment @gitlab-bot label <label1> <label2> to add labels to your MR. Please see the list of allowed labels in the label command documentation.

This message was generated automatically. You're welcome to improve it.

added Community contribution workflowin dev labels

assigned to @mbroa04

This merge request will be considered part of the quarterly GitLab Hackathon for a chance to win a prize.

Can you make sure this merge request mentions or links to the relevant issue that it's attempting to close?

Thank you for your contribution!

This message was generated automatically. You're welcome to improve it.

added Hackathon label

added 1st contribution label

mentioned in issue gitlab-org/quality/triage-reports#8623 (closed)

approved this merge request

@mbroa04 Looks good to me, thanks!

changed milestone to %15.3

added docsfix documentation maintenancerefactor workflowin review + 1 deleted label and removed workflowin dev label

requested review from @rymai

added typemaintenance label

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

doc/administration/audit_events.md

The review does not need to block merging this merge request. See the:

Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
The Technical Writer assigned for that stage and group.
Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

@aqualls Could you please review? Thanks!

requested review from @aqualls and removed review request for @rymai

approved this merge request

added Technical Writing label

added devopsfoundations groupcompliance labels and removed 1 deleted label

Yep, part of the ongoing cleanup we've been doing to standardize our linking. Linters standardization.

@mbroa04 looks good! I've approved. Rémy ran a pipeline, so I can safely merge.

@rymai Strange: I can't merge this MR, even though we've both approved it:

Requires 1 approval from Code Owners. Approved by you and others

Ideas on how to proceed?

Aha, @mwoolf can approve / merge. Sending this work over to him.

requested review from @mwoolf

approved this merge request

resolved all threads

enabled an automatic merge when the pipeline for 42c6c6b1 succeeds

merged

@mbroa04, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

Leave a or a on this comment to describe your experience.
Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

Have five minutes? Take our survey to give us even more feedback on how GitLab can improve the contributor experience.

Thanks for your help!

This message was generated automatically. You're welcome to improve it.