Skip to content

Protect repositories #3

@Crocmagnon

Description

@Crocmagnon

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:

  • protecting some repositories manually, because we may want to keep them even if all other "protections" fail
  • protecting repositories based on last activity instead of creation date
  • protecting repositories based on open PRs in the upstream repo
  • protecting repositories based on unmerged branches (with recent activity?)

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).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions