You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
This PR adds a target to the Makefile to generate the CODEOWNERS file
locally without a GitHub PAT.
<!-- Issue number (e.g. #1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixes#40072
<!--Describe what testing was performed and which tests were added.-->
#### Testing
Added myself to a random receiver as a code owner and ran `make
gencodeowners`. It generated the `CODEOWNERS` file correctly without
requiring me to have a GitHub PAT (I do not have one set up).
<!--Describe the documentation added.-->
#### Documentation
Added reference in `CONTRIBUTING.md` and in the `check-codeowners`
GitHub Action error message.
<!--Please delete paragraphs that you did not use before submitting.-->
git diff -s --exit-code || (echo 'Generated code is out of date, please apply this diff and commit the changes in this PR.' && git diff && exit 1)
62
+
git diff -s --exit-code || (echo 'Generated code is out of date, please run "make gencodeowners" or apply this diff and commit the changes in this PR.' && git diff && exit 1)
- Type `make update-codeowners`. This will trigger the regeneration of the `.github/CODEOWNERS` file and the [metadata generator](https://github.com/open-telemetry/opentelemetry-collector/blob/main/cmd/mdatagen/README.md#using-the-metadata-generator) to generate the associated code/documentation.
196
+
- Type `make generate`. This will trigger the [metadata generator](https://github.com/open-telemetry/opentelemetry-collector/blob/main/cmd/mdatagen/README.md#using-the-metadata-generator) to generate the associated code/documentation.
197
+
- Type `make gencodeowners`. This will trigger the regeneration of the `.github/CODEOWNERS` file.
197
198
198
199
When submitting a component to the community, consider breaking it down into separate PRs as follows:
0 commit comments