Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork0
Bash scripts to work with the Github API
License
locus313/github-api-scripts
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
⭐ If you like this project, star it on GitHub — it helps a lot!
Overview •Getting started •Scripts •Resources
A collection of standalone bash scripts for GitHub organization administration. Automate common tasks like bulk permission management, repository creation, migration, and reporting using simple, self-contained utilities powered by the GitHub REST API.
This toolkit provides ready-to-use automation scripts for GitHub organization administrators. Each script is a complete, independent utility—no shared libraries or frameworks. Just drop in your token and organization name, and you're ready to go.
What you can do:
- Grant team permissions across all repositories in bulk
- Create repositories from templates with pre-configured access
- Mirror repositories with full git history
- Generate monthly issue reports with contributor statistics
- Track license consumption for enterprise accounts
What you can do:
- Grant team permissions across all repositories in bulk
- Create repositories from templates with pre-configured access
- Mirror repositories with full git history
- Generate monthly issue reports with contributor statistics
- Track license consumption for enterprise accounts
Built with simplicity: Each script uses onlycurl for API requests andjq for JSON processing—no complex dependencies, no installation required beyond standard Unix tools.
Note
These scripts follow a convention-over-configuration approach. Each lives in its own directory as a single.sh file with built-in validation and error handling.
- bash 4+
- curl - HTTP client for API requests
- jq - Command-line JSON processor
- git - For repository operations (required by some scripts)
- GitHub Personal Access Token with appropriate scopes
Clone the repository:
git clone https://github.com/locus313/github-api-scripts.gitcd github-api-scriptsAlternatively, download individual scripts as needed—each script is standalone and can be used independently.
Create a GitHub Personal Access Token atgithub.com/settings/tokens with these scopes:
repo- Full control of repositoriesadmin:org- Organization administrationread:enterprise- Read enterprise data (for license scripts)
Export your token as an environment variable:
export GITHUB_TOKEN="ghp_your_token_here"
Tip
Add this export to your~/.bashrc or~/.zshrc to persist the token across terminal sessions.
Scripts use environment variables for configuration. Common variables include:
| Variable | Description | Required |
|---|---|---|
GITHUB_TOKEN | GitHub personal access token | Yes |
ORG | Organization name | Yes (most scripts) |
API_URL_PREFIX | GitHub API base URL (default:https://api.github.com) | No |
GIT_URL_PREFIX | GitHub base URL (default:https://github.com) | No |
Note
The*_PREFIX variables support GitHub Enterprise Server. Set them to your enterprise domain to use these scripts with GHES.
Each script is a self-contained utility designed for a specific task. Navigate to the script's directory, set the required environment variables, and execute.
Script:github-add-repo-permissions/github-add-repo-permissions.sh
Grants team permissions across all repositories in an organization. Supports multiple permission levels (admin, maintain, push, triage, pull) and multiple teams per permission level.
Required variables:
export GITHUB_TOKEN="your_token"export ORG="your-org"# Set one or more permission levels (space-separated team slugs)export REPO_ADMIN="platform-team ops-team"# Admin permissionsexport REPO_MAINTAIN="maintainers"# Maintain permissionsexport REPO_PUSH="developers contributors"# Write/push permissionsexport REPO_TRIAGE="support-team"# Triage permissionsexport REPO_PULL="external-auditors"# Read/pull permissions
Usage:
cd github-add-repo-permissions./github-add-repo-permissions.shWhat it does:
- Retrieves all repositories in the organization (paginated)
- Grants permissions to specified teams based on permission level
- Supports multiple teams per permission level (space-separated)
- Processes all five GitHub permission levels: admin, maintain, push, triage, pull
- Includes 5-second delays between repos to avoid rate limits
Permission levels:
admin- Full repository access including settings and team managementmaintain- Repository management without admin privilegespush- Read and write access to codetriage- Read access plus ability to manage issues and pull requestspull- Read-only access to code
Note
At least one permission level must be set. Team slugs should be lowercase and hyphenated (e.g., "Platform Team" →platform-team).
Script:github-repo-from-template/github-repo-from-template.sh
Creates a new repository from a template with pre-configured team permissions and collaborator access.
Required variables:
export GITHUB_TOKEN="your_token"export ORG="your-org"export TEMPLATE_REPO="template-repo"export REPO_ADMIN="admins platform-team"# Space-separated team slugsexport REPO_WRITE="developers contributors"# Space-separated team slugsexport CD_USERNAME="ci-bot"export CD_GITHUB_TOKEN="bot_token"
Usage:
cd github-repo-from-template./github-repo-from-template.sh new-project-nameWhat it does:
- Creates a private repository from the specified template
- Includes all branches from the template
- Assigns admin permissions to teams in
REPO_ADMIN - Assigns write permissions to teams in
REPO_WRITE - Invites CD user as collaborator and auto-accepts the invitation
Script:github-import-repo/github-import-repo.sh
Performs a full repository mirror—clones source repo and pushes all branches, tags, and history to a new destination repo.
Required variables:
export GITHUB_TOKEN="your_token"export ORG="your-org"export OWNER_USERNAME="admin-user"
Usage:
cd github-import-repo./github-import-repo.sh source-repo destination-repoWhat it does:
- Creates a new internal repository
- Performs bare clone of source repository
- Mirrors all git objects to destination
- Grants admin permissions to specified owner
- Cleans up local temporary clone
Warning
This creates a complete copy with full git history. Ensure you have sufficient disk space and network bandwidth for large repositories.
Script:github-monthly-issues-report/github-monthly-issues-report.sh
Generates HTML-formatted statistics about issues created within a date range, filtered by labels.
Required variables:
export GITHUB_TOKEN="your_token"export ORG="your-org"export REPO="your-repo"export MONTH_START="2025-10-01"export MONTH_END="2025-10-31"
Usage:
cd github-monthly-issues-report./github-monthly-issues-report.shWhat it does:
- Filters issues by creation date range
- Filters by label (currently hardcoded to
Linked [AC]) - Uses timeline API to track who applied labels
- Generates author and contributor statistics
- Outputs HTML report to
output.txt
Note
This script includes a hardcoded label filter. Edit the script to modify the filter criteria.
Script:github-get-consumed-licenses/github-get-consumed-licenses.sh
Retrieves license consumption metrics for a GitHub Enterprise account.
Required variables:
export GITHUB_TOKEN="your_enterprise_token"# Must have read:enterprise scopeexport ENTERPRISE="your-enterprise"
Usage:
cd github-get-consumed-licenses./github-get-consumed-licenses.shOutput:
Total seats consumed: 150Total seats purchased: 200What it does:
- Calls the enterprise consumed-licenses endpoint
- Uses Bearer token authentication (unlike other scripts)
- Returns seat consumption and purchase counts
Important
This script requires an enterprise-level token withread:enterprise scope. Organization tokens will not work.
Test on a test organization firstThese scripts have no dry-run mode. Always validate on a non-production organization before running against production resources.
Rate limitingScripts include built-in delays (5 seconds between repository operations) to stay within GitHub's rate limits. For large organizations with hundreds of repos, expect longer execution times.
Audit trailsCapture output for compliance and troubleshooting:
./script.sh2>&1| tee execution-$(date +%Y%m%d).log
Team slugs vs display namesGitHub API uses team slugs (lowercase, hyphenated). Example: "Platform Team" →platform-team. Find team slugs in your organization settings or via the API.
GitHub Enterprise ServerThese scripts support GHES. Set custom endpoints:
export API_URL_PREFIX="https://github.company.com/api/v3"export GIT_URL_PREFIX="https://github.company.com"
About
Bash scripts to work with the Github API
Topics
Resources
License
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Sponsor this project
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.