-
Notifications
You must be signed in to change notification settings - Fork 27
dot-project maintainer validation #385
Copy link
Copy link
Open
Labels
area/dot-projectutilities/dot-project scaffolding and bootstrap toolingutilities/dot-project scaffolding and bootstrap toolingkind/choreChore or maintenanceChore or maintenanceneeds-groupIndicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)Indicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)needs-statusIndicates an issue or PR missing a status labelIndicates an issue or PR missing a status labelpriority/mediumMedium priorityMedium prioritytriage/validIssue or PR is valid with enough information to be actionableIssue or PR is valid with enough information to be actionable
Metadata
Metadata
Assignees
Labels
area/dot-projectutilities/dot-project scaffolding and bootstrap toolingutilities/dot-project scaffolding and bootstrap toolingkind/choreChore or maintenanceChore or maintenanceneeds-groupIndicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)Indicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)needs-statusIndicates an issue or PR missing a status labelIndicates an issue or PR missing a status labelpriority/mediumMedium priorityMedium prioritytriage/validIssue or PR is valid with enough information to be actionableIssue or PR is valid with enough information to be actionable
Once we populate a project's maintainer yaml, we should auto create an issue to validate it and hand it off to @riaankleinhans