Thank you for publishing this tool!
We use this very conveniently.
I'd like to share an example that demonstrates how to report the precise changes made to a CODEOWNERS file within a pull request, which could potentially be useful to others. As you may already be aware, interpreting .github/CODEOWNERS can be quite intricate.
To simplify this process, I've crafted a GitHub Action that provides detailed insights into which files are specifically affected by modifications to .github/CODEOWNERS.
(This issue is not a problem report.)
Thank you for publishing this tool! We use this very conveniently.
I'd like to share an example that demonstrates how to report the precise changes made to a CODEOWNERS file within a pull request, which could potentially be useful to others. As you may already be aware, interpreting .github/CODEOWNERS can be quite intricate.
To simplify this process, I've crafted a GitHub Action that provides detailed insights into which files are specifically affected by modifications to .github/CODEOWNERS.
This action will add a report comment like the one below when a pullrequest is opened that modifies .github/CODEOWNERS.
Now, armed with this handy diff report, you can tweak .github/CODEOWNERS with confidence, no more guesswork involved!
Anyway, big thanks for making all of this possible!