add codeownership areas #1528
add codeownership areas #1528
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Co-authored-by: Copilot <[email protected]>
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Alan-eMartin
requested review from
andrijapau,
doctorperceptron,
alvaro-at-xanadu and
ashishks0522
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
There was a problem hiding this comment.
Pull Request Overview
This PR establishes code ownership rules by creating a new .github/CODEOWNERS file that assigns specific directories and files to appropriate teams for code review and maintenance responsibilities.
- Creates a comprehensive CODEOWNERS file with team assignments for different parts of the codebase
- Assigns software-related files and directories to @software-cloud team
- Assigns documentation and demonstration content to @Content-Team with fallback ownership to @core-release-managers
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Alan-eMartin
force-pushed
the
sc-98101-create-code-owners-for-the-qml-repository
branch
from
b137575 to
07f624f
Compare
There was a problem hiding this comment.
I would say we can also add @software-cloud as owner for the following
- metadata_schemas
- notebook_converter - are we adding owners for this?
All done |
This pull request adds a new
.github/CODEOWNERSfile to the repository. The file specifies which teams are responsible for various parts of the codebase, helping to clarify ownership and streamline code review processes.