Create a CODEOWNERS file as described in the Github documentation above and assign responsible code owners. This file should be created in the .github directory. For now we can assign the following rules:
[ ] Add @rak3rman as a code owner of * (default code owner for everything, this line should be first in the file), provide comments explaining what this does (see linked docs)
[ ] Add @rak3rman as a code owner of .github, provide comments explaining what is contained within this directory
[ ] Add @rak3rman as a code owner of /hono, provide comments explaining what is contained within this directory
[ ] Add @rak3rman as a code owner of /next, provide comments explaining what is contained within this directory
The last 3 tasks seem redundant since @rak3rman is already the code owner of everything, but providing this templating now will be beneficial in the future when new code owners are added.
Description
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
Create a CODEOWNERS file as described in the Github documentation above and assign responsible code owners. This file should be created in the
.githubdirectory. For now we can assign the following rules:*(default code owner for everything, this line should be first in the file), provide comments explaining what this does (see linked docs).github, provide comments explaining what is contained within this directory/hono, provide comments explaining what is contained within this directory/next, provide comments explaining what is contained within this directoryThe last 3 tasks seem redundant since @rak3rman is already the code owner of everything, but providing this templating now will be beneficial in the future when new code owners are added.
Acceptance Criteria
.githubdirectory*, provide comments (1-3 lines).github, provide comments (1-3 lines)/hono, provide comments (1-3 lines)/next, provide comments (1-3 lines)