Skip to content
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 security and coverage scanning to best practices for new repos #741

Merged
merged 2 commits into from
Jun 16, 2021

Conversation

arminru
Copy link
Member

@arminru arminru commented May 27, 2021

In open-telemetry/oteps#144 and open-telemetry/opentelemetry-specification#1333 CodeQL security scanning was enabled for most of our repositories and most of them already have Codecov coverage scanning set up. I think we should mention this in the new repo best practices so it's also considered right from the start when new repositories are created.

Copy link
Member

@alolita alolita left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding this guideline to OTel's best practices for new repos.


1. Only set "Allow squash merging" for the Merge button. It will ensure clean
history for the repository.
2. Set up a security scanning tool like, for example, [Github CodeQL](https://docs.github.com/en/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning).
3. Set up a test coverage scanning tool like, for example, [Codecov](https://codecov.io/).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

anything needs to be said about the recent security issue with codecov? What's the best practices now?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added it as an example based on the fact that most of our repos already use it: https://codecov.io/gh/open-telemetry. It would be odd to advise against using it while it's already being used heavily. If you think we should reconsider it and look for alternatives, we can leave it out as an example for now and tackle this separately.

@yurishkuro yurishkuro merged commit 8b0922c into main Jun 16, 2021
@yurishkuro yurishkuro deleted the repo-best-practices branch June 16, 2021 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants