Add GITHUB_EXCLUDED_ORGS support for organization filtering #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add GITHUB_EXCLUDED_ORGS Environment Variable for Organization Filtering
Problem
Users deploying gitea-mirror in environments with IP restrictions (like Proxmox/LXC) encounter sync failures when GitHub organizations have IP allowlists enabled. The entire sync process would crash with a 403 Forbidden error.
Solution
Added
GITHUB_EXCLUDED_ORGS
environment variable to proactively exclude specific organizations from the sync process.Changes
GITHUB_EXCLUDED_ORGS
accepts a comma-separated list of organization names to excludedocker-compose.yml
anddocker-compose.dev.yml
docs/BUILD_GUIDE.md
with usage exampleUsage
# Exclude organizations with IP restrictions or that shouldn't be synced GITHUB_EXCLUDED_ORGS=private-org,restricted-org,test-org
Benefits
Fixes issues with IP allowlist restrictions in enterprise/restricted environments. #46