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

chore: add CODEOWNERS file #5213

Merged
merged 15 commits into from
Nov 4, 2024
Merged

chore: add CODEOWNERS file #5213

merged 15 commits into from
Nov 4, 2024

Conversation

Akuukis
Copy link
Contributor

@Akuukis Akuukis commented Oct 30, 2024

Checklist

  1. If you've added code that should be tested, add tests
  2. If you've changed APIs, update (or create!) the documentation
  3. Ensure the tests pass
  4. Run ./python-format.sh to make sure that your code lints and that you've followed our coding style
  5. Write a title and, if necessary, a description of your work suitable for publishing in our release notes
  6. Mention any related issues in this repository (as #ISSUE) and in other repositories (as kobotoolbox/other#ISSUE)
  7. Open an issue in the docs if there are UI/UX changes
  8. Create a testing plan for the reviewer and add it to the Testing section
  9. Add frontend or backend tag and any other appropriate tags to this pull request

Description

Internal process configuration with no changes to the product.

Notes

Let's declare ownership of code. Please comment or directly push to this PR to add yourself (or others) to CODEOWNERS before approving. Read more in internal docs. In short:

  • add yourself if you or others consider you a subject expert of that code, or
  • add yourself if you want to always receive review requests on changes of that code

Testing

Not testable. After merging, should suggest reviewers based on the CODEOWNERS file according to github docs.

Copy link
Contributor

@rgraber rgraber left a comment

Choose a reason for hiding this comment

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

Added myself for audit logs. LGTM

Copy link
Contributor

@pauloamorimbr pauloamorimbr left a comment

Choose a reason for hiding this comment

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

LGTM!

@magicznyleszek
Copy link
Member

Looks good. I will wait for everyone to take what they want, and I will have the rest 🤑

Remove my name from files I never touched, added @bufke, @jnm and @JacquelineMorrissette for files they should own.
Copy link
Contributor

@noliveleger noliveleger left a comment

Choose a reason for hiding this comment

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

.github/CODEOWNERS Outdated Show resolved Hide resolved
…and John, and group these entries together
…as the backend lead developer. `CONTRIBUTING.md` applies equally to the
backend, and `kpi.code-workspace` contains various settings related to
formatting and linting Python code
@jnm
Copy link
Member

jnm commented Nov 1, 2024

@jnm, @bufke , @JacquelineMorrissette please review my changes

@noliveleger, I have contradicted a few of them. You can see my rationale in my commit messages. LMK if you want to discuss anything

@Akuukis
Copy link
Contributor Author

Akuukis commented Nov 2, 2024

Sorted, grouped and clarified that last line wins. Added the missing github folder, set @p2edwards as owner for patches folder as per his 👍 above.

@Akuukis Akuukis merged commit bd4824b into main Nov 4, 2024
7 checks passed
@Akuukis Akuukis deleted the codeowners branch November 4, 2024 10:05
@p2edwards p2edwards added the workflow Related to development process label Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
workflow Related to development process
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants