-
Notifications
You must be signed in to change notification settings - Fork 0
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
Protect repositories #3
Comments
Thank you for the ideas; they are great! I really like the idea of deleting repositories based on the last activity date, rather than the creation date. This can be done without changing the external flag. Also, a I'll start tackling tasks from the lowest level of complexity to the highest. Also, feel free to open a PR if you have strong opinions about the implementation. |
Version 0.2.0 now:
|
Nice ! 😀 |
Yeah, a PR guard would be nice I agree. But at the same time, it's hard to track that without consuming some event. Listing why a repo was filtered out seems like an easy low-hanging fruit. |
After doing some exploration, it looks like the open PR feature can be implemented quite easily with the GraphQL API but would require several calls with the REST API. |
Hello! Thank you for this nice tool, I wanted to do some cleanup in my forks but unfortunately I'd need some more features to use it.
There are many reasons a fork may need to stay even if it's old. Maybe a branch is unmerged and we're still working on it, maybe a PR is open waiting for a review.
It also appears that the tool only filters forks by their
createdAt
date.I'm actively working on a fork and I regularly push commits & branches and they get merged regularly, so I don't want to delete this fork.
I suggest adding several features to make the tool useful to more people:
The output should mention clearly why a repo is being protected or if it's being deleted (or would be, in case the
-delete
flag is not provided).The text was updated successfully, but these errors were encountered: