-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a warning if we are removing all users from CODEOWNERS #11
Comments
This issue is stale because it has been open 21 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
How would folks like to see this warning? in the command line and dont create a pull request? or should we create the pull request and put the warning in the pull request description so folks dont merge through an empty |
In my humble opinion, I believe we should draw inspiration from GitHub's stale-repos project. An organization is likely to run workflows like stale-repos, cleanowners, and others from a single repository, allowing the workflow to examine the entire organization. For instance, the stale-repos action/workflow could maintain an issue with a list of stale repositories. Similarly, cleanowners could maintain an issue with lists of:
By doing so, we can streamline our workflow and ensure that our organization's repositories are well-maintained and up-to-date. |
@electriquo I like that idea! I think I'll add a report and issue creation as well as printing a warning to the terminal during the workflow run. |
No description provided.
The text was updated successfully, but these errors were encountered: