Skip to content
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 options for excluding archives and forks #11

Open
jwodder opened this issue Dec 12, 2023 · 0 comments
Open

Add options for excluding archives and forks #11

jwodder opened this issue Dec 12, 2023 · 0 comments
Labels
configuration Telling the program what to do enhancement New feature or request therefor high priority Work on these first under consideration Dev has not yet decided whether or how to implement

Comments

@jwodder
Copy link
Owner

jwodder commented Dec 12, 2023

Possible levels at which this could be configured:

  • Add archives = BOOL and forks = BOOL fields (default values True) under [reponews.repos] for including/excluding all archives and/or forks

  • Support specifying archives and forks on a per-owner level, possibly via something like:

    [reponews.repos]
    include = [
        # Like "some-user/*", but with options:
        { owner = "some-user", archives = BOOL, forks = BOOL }
        # Setting one or both options to `true` overrides a corresponding `false` setting
        # for `reponews.repos.{archives,forks}`
    ]
  • Support applying archive & fork filters to just affiliated repositories somehow

    • Add archives = BOOL and forks = BOOL fields under [reponews.activity.affiliated]?
    • I don't think there's an efficient way to check which affiliation an affiliated repository has, so per-affiliation filters aren't an option
    • What should happen if a given archive or fork repository is included via both affiliation and inclusion but the corresponding filters disagree?
@jwodder jwodder added enhancement New feature or request therefor configuration Telling the program what to do labels Dec 12, 2023
@jwodder jwodder added the under consideration Dev has not yet decided whether or how to implement label May 2, 2024
@jwodder jwodder added the high priority Work on these first label Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
configuration Telling the program what to do enhancement New feature or request therefor high priority Work on these first under consideration Dev has not yet decided whether or how to implement
Projects
None yet
Development

No branches or pull requests

1 participant