-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CI testing for metadata.yaml for all components. #23376
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This PR uses the checkfile tool introduced in open-telemetry/opentelemetry-go-build-tools#348 in order to validate the presence of the metadata.yaml file in all components. It also removes the checkdoc tool in favor of the checkfile tool, which is now also used to validate the presence of README.md. Issue: open-telemetry#23376
#24643) **Description:** This PR uses the checkfile tool introduced in open-telemetry/opentelemetry-go-build-tools#348 in order to validate the presence of the metadata.yaml file in all components. It also removes the checkdoc tool in favor of the checkfile tool, which is now also used to validate the presence of README.md. **Link to tracking Issue:** #23376
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Three tasks are complete, closing issue. |
Component(s)
cmd/mdatagen
Describe the issue you're reporting
The proposal is that for all components, the CI test will check:
metadata.yaml
file. (PR)receiver|processor|exporter|connector|extension
for class). (PR)The text was updated successfully, but these errors were encountered: