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

[OpenSSF] Use CODEOWNERS configuration #1605

Closed
Zeitsperre opened this issue Jan 17, 2024 · 1 comment
Closed

[OpenSSF] Use CODEOWNERS configuration #1605

Zeitsperre opened this issue Jan 17, 2024 · 1 comment
Assignees
Labels
information For development/intsructional purposes standards / conventions Suggestions on ways forward

Comments

@Zeitsperre
Copy link
Collaborator

In the process of raising our OpenSSF rating, I've stumbled across the feature to have dedicated CODEOWNERS. This provides the ability to specify that certain files or certain folders are identified as the responsibility of particular users. Some good examples of how this could look off the top of my head:

  • xclim/indices: huard, tlogan2000, Zeitsperre
  • xclim/sdba/*.py: aulemahal, huard
  • .github/*/*.yml: Zeitsperre

Specifying these users being the CODEOWNERS would mean that someone listed as an owner must be the reviewer of any Pull Requests affecting those files. This prevents cases where Pull Requests go really far out of scope, as more reviewer approvals would be needed. The category affected is "Branch Protection"

This suggestion comes from OpenSSF. We are in no way obligated to enact this kind of change, but adopting this measure will help raise our rating.

For more info about CODEOWNERS, see: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

@Zeitsperre Zeitsperre added standards / conventions Suggestions on ways forward information For development/intsructional purposes labels Jan 17, 2024
@Zeitsperre Zeitsperre self-assigned this Jan 17, 2024
@Zeitsperre
Copy link
Collaborator Author

Closing. Not yet relevant for our needs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
information For development/intsructional purposes standards / conventions Suggestions on ways forward
Projects
None yet
Development

No branches or pull requests

1 participant