Skip to content

Update config and excludeReposByName to support micromatch patterns for more flexible repo exclusion #69

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

Closed
Steven-Nagie opened this issue Nov 14, 2024 · 0 comments

Comments

@Steven-Nagie
Copy link
Contributor

Wondering what your thoughts would be for a PR that would allow users to exclude repos for a given micromatch pattern? My use case is that I'm part of a GitLab group with dozens of subgroups and 400+ projects. It's easier for me to exclude the projects I don't want than to specifically include the groups I do want. I've been running the project locally with the changes and it fits my use case well. Example:

{
  "$schema": "./schemas/v2/index.json",
  "repos": [
    {
      "type": "gitlab",
      "token": "{{token}}",
      "users": [
        "{{user}}"
      ],
      "groups": [
        "fake-group"
      ],
      "exclude": {
        "projects": [
          "fake-group/devops/**",
          "fake-group/lambdas/**",
          "fake-group/architecture/**"
        ]
      }
    }
  ]
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants