Auto-discover repositories across a GitHub organization and generate Argo CD Applications with the ApplicationSet SCM Provider generator
domain: argo-cd.readthedocs.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an ApplicationSet with a generators.scmProvider.github block specifying the target GitHub organization (and, for GitHub Enterprise, the API URL).
Reference a Kubernetes Secret containing a GitHub token via tokenRef, or omit it to make unauthenticated, rate-limited, public-repos-only requests.
Add filters (e.g. matching a repository name pattern, or requiring a specific file or label to exist) so only relevant repositories are discovered rather than every repo in the org.
Decide whether to scan only each repo's default branch (the default behavior) or set allBranches: true to also generate an item per branch.
Define the Application template using generator outputs such as {{ url }}, {{ repository }}, and {{ branch }} so each generated Application points at the correct repo and branch.
Known gotchas
Without filters, the generator creates an Application for every repository the token can see in the org, which can flood the cluster with unwanted Applications on a large organization.
Unauthenticated requests (no tokenRef) hit GitHub's low anonymous rate limit and can only see public repositories — private-repo discovery silently returns nothing without a token.
allBranches: true multiplies discovered items by branch count per repository, producing far more Applications than expected if stale feature branches aren't cleaned up.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?