OpenAPITools / OpenAPITools/openapi-generator

[REQ][repo] Use CODEOWNERS

Open
#4,177 5 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement: Feature
Dominant language
Java
Stars
26.8k
Forks
7.7k
PR merge metrics
PR metrics pending

Description

Is your feature request related to a problem? Please describe.

The PR Checklist states

Copy the technical committee to review the pull request if your PR is targeting a particular programming language.

This step can be automated using CODEOWNERS making it easier for everyone 👯‍♂

Describe the solution you'd like

By placing CODEOWNERS file in the .github folder language specific people/teams can be auto assigned to review PRs in their field of expertise.

Here's an example/start

# Core
/modules/* @OpenAPITools/generator-core-team
/modules/openapi-generator-cli/ @OpenAPITools/generator-core-team
/modules/openapi-generator-core/ @OpenAPITools/generator-core-team
/modules/openapi-generator-gradle-plugin/ @OpenAPITools/generator-core-team
/modules/openapi-generator-maven-plugin/ @OpenAPITools/generator-core-team
/modules/openapi-generator-online/ @OpenAPITools/generator-core-team

# TypeScript Clients
## folders
**/*typescript*/** @TiFu @taxpon @sebastianhaas @kenisteward @Vrolijkx @macjohnny @nicokoenig @topce @akehir
## files
**/*TypeScript* @TiFu @taxpon @sebastianhaas @kenisteward @Vrolijkx @macjohnny @nicokoenig @topce @akehir
**/*typescript* @TiFu @taxpon @sebastianhaas @kenisteward @Vrolijkx @macjohnny @nicokoenig @topce @akehir

Additional context

I don't have access to https://github.com/OpenAPITools/teams so I can't tell if each language or client have a separate team. If there is then it might be a good idea to use them.

I also don't know to whom every file should be assigned so I have assumed that files and folders called something with {LANG} belongs to the respective technical committee, everything else is Core.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the PR Checklist and GitHub's CODEOWNERS behavior. Create the proposed CODEOWNERS file in .github, first confirming which language and core teams are available and which paths they own. Done means pull requests are automatically assigned to the appropriate reviewers without the manual checklist step.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
developer-experience
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.