-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Ensure that all codeowners are members of the OpenTelemetry organization #30552
Comments
I am unable to check the checkbox for my name, but I have seen the issue.
|
I am now a member of the OpenTelemetry GitHub Org. |
Just adding a couple reference issues @braydonk - open-telemetry/community#1877 |
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 |
"zdaratom" is no longer needed as it has been updated via #30639 |
Sorry, please use |
This PR introduces a check backed by a github token that tests the content of .github/CODEOWNERS against the metadata of all the components. Given that a token is used, and won't be present in builds running with forks, this check is only made on the main branch of the repository `open-telemetry/opentelemetry-collector-contrib`. As such, I can't really test if it all works. The token is provisioned by open-telemetry/community#1659. More context in #30552
As of 2024/04/30:
|
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 |
not stale, codeowners check should pass |
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 |
After a long wait, a few of the folks here are still not members of the OpenTelemetry organization. Unfortunately, it is time to move you to emeritus. See #36229 If you have any problem with this approach, please get in touch. |
Sorry, I'm just seeing this now. Can i open a request? |
@emreyalvac please do, please feel free to name me as one of your 2 sponsors. |
Hi @atoulme, Thank you very much for your understanding. I need one more sponsor. I am trying to find a sponsor. |
@emreyalvac welcome and thank you for taking action! |
Actually, I thank you for your understanding. |
Component(s)
No response
Describe the issue you're reporting
See #20868 for the last campaign
Not all codeowners of this repository are members of the OpenTelemetry github organization, which membership is associated with membership of the OpenTelemetry project.
The guidelines enforce membership because it allows to assign and ping codeowners on issues or pull requests. Unfortunately, if you try to create an issue or assign a PR to a codeowner who is not member of OpenTelemetry, the workflow fails. I would like to fix this issue.
Going forward, I would also ideally like to make sure that we check that codeowners are members of the github organization whenever the codeowners file is touched.
The process to become a member of OpenTelemetry is straightforward. Open this issue template on the community project to get started.
I have identified a list of codeowners who are not currently members of OpenTelemetry. I will ping them in this issue below.
Thank you and apologies for the inconvenience.
The text was updated successfully, but these errors were encountered: