Dataweaver starter folder#347
Conversation
Restrict top-level folders to org owners to limit new folder creation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a CODEOWNERS file to manage repository ownership and a placeholder README.md for the Data Weaver experiment. Feedback suggests including global owners in the specific directory pattern to ensure oversight and expanding the documentation to include a project description and goals.
| * @datacommonsorg/owners | ||
|
|
||
| # Data Weaver stand-alone app. | ||
| dataweaver/ @beets @nick-nlb @miss-o-soup |
There was a problem hiding this comment.
In GitHub CODEOWNERS, the last matching pattern takes precedence. By defining dataweaver/ here, the global owners (@datacommonsorg/owners) defined on line 5 will be excluded from review requests for this directory. Given the goal of adding controls to 'prevent sprawl', consider including the global owners team here to maintain oversight. Additionally, per the guidance on line 2, consider using a team handle instead of individual users if one is available for this project.
dataweaver/ @datacommonsorg/owners @beets @nick-nlb @miss-o-soup
| @@ -0,0 +1 @@ | |||
| # Data Weaver Experiment | |||
There was a problem hiding this comment.
The README is currently very sparse. To provide better context and help manage the 'sprawl' mentioned in the PR description, please include a brief description of the project's purpose, its current status as an experiment, and its scope.
| # Data Weaver Experiment | |
| # Data Weaver Experiment | |
| ## Description | |
| [Add a brief description of the experiment and its goals.] |
2 participants
Add more controls to the repo to prevent sprawl.