Protect repositories about fork-sweeper HOT 5 OPEN

Version 0.2.0 now:

• Fetches forked repos based on pushed_at || updated_at || created_at date.

• Lists the forked repositories that will and won't be deleted:

  fork-sweeper --owner rednafi --token $GITHUB_TOKEN --older-than-days 0

  This returns:

  Fetching forked repositories for rednafi...
  
  Guarded forked repos [won't be deleted]:
  
  Unguarded forked repos [will be deleted]:
      - https://github.com/rednafi/cpython
      - https://github.com/rednafi/dysconfig
      - https://github.com/rednafi/pydantic

• Explicitly filter out forked repositories with fuzzy name matching:

  fork-sweeper --owner "rednafi" --token $GITHUB_TOKEN --older-than-days 0 --guard 'py'

  This prints:

    Fetching forked repositories for rednafi...
  
    Guarded forked repos [won't be deleted]:
        - https://github.com/rednafi/cpython
        - https://github.com/rednafi/pydantic
  
    Unguarded forked repos [will be deleted]:
        - https://github.com/rednafi/dysconfig

from fork-sweeper.

Nice ! 😀
I think however the biggest value would come from an "open PR" guard. It may require some more work though as I don't know if this information can easily be obtained with GitHub's API.
Also, listing why repos are protected would be a good addition too IMO.

from fork-sweeper.

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 --protect flag that will take a list of repositories sounds useful.

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.

from fork-sweeper.

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.

from fork-sweeper.

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.
There’s a discussion on the refined-github repo about this, specifically this comment: refined-github/refined-github#2268 (comment)

from fork-sweeper.