Skip to content

Exclude description templates from required approvals

Marcel Amirault requested to merge codeowners-for-markdownlint into master

What does this MR do and why?

In !97906 (comment 1100141853) we noticed that we couldn't approve changes to the description templates, but these files are all pure markdown, so maybe they don't need to be part of the required approvals?

As an alternative, we could add @susantacker @dianalogan @kpaizee @sselhorn to the top-level * rule, so they can approve merges to files that "fall through the cracks"?

As part of this MR, I've also added a / to the entry for /doc/.markdownlint, because this is actually a directory, not a file (/doc/.markdownlint/).

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports