We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
TC and GC discussed and decided that we want to make Github security reporting capabilities the primary reporting channel.
We will need to update the policy document and make sure all repos have the vulnerability reporting feature enabled (including new repos).
cc @open-telemetry/governance-committee @open-telemetry/technical-committee
The text was updated successfully, but these errors were encountered:
PR to the policy attached.
Sorry, something went wrong.
I enabled "Private vulnerability reporting" on all repos. Wish GitHub would have org-level settings that would override individual repo defaults.
turns out GitHub does support bulk updates of security settings, but the vulnerability reporting is not one of them, perhaps because it itself is in beta: https://docs.github.com/en/enterprise-cloud@latest/code-security/security-overview/enabling-security-features-for-multiple-repositories
reyang
No branches or pull requests
TC and GC discussed and decided that we want to make Github security reporting capabilities the primary reporting channel.
We will need to update the policy document and make sure all repos have the vulnerability reporting feature enabled (including new repos).
cc @open-telemetry/governance-committee @open-telemetry/technical-committee
The text was updated successfully, but these errors were encountered: