This directory contains configuration and documentation for GitHub CLI integration with the Kob Git Updater project.
# 1. Setup GitHub CLI for this repository
make gh-setup
# 2. Verify authentication and access
make gh-statusmake gh-status # Show repository status, PRs, and issues
make gh-releases # List all releases
make gh-release # Create release for current versionmake gh-pr # Create pull request from current branch
make gh-issues # List open issues
make gh-workflows # Show GitHub Actions workflows
make gh-runs # Show recent workflow runsOnce authenticated, you can use these gh commands directly:
gh repo view # View repository information
gh repo clone owner/repo # Clone repository
gh repo fork # Fork repositorygh pr list # List pull requests
gh pr create # Create new pull request
gh pr checkout 123 # Checkout PR #123
gh pr merge 123 # Merge PR #123
gh pr review 123 # Review PR #123gh issue list # List issues
gh issue create # Create new issue
gh issue close 123 # Close issue #123
gh issue reopen 123 # Reopen issue #123gh release list # List releases
gh release view v1.3.0 # View specific release
gh release create v1.3.1 # Create new release
gh release upload v1.3.1 *.zip # Upload assets to releasegh workflow list # List workflows
gh workflow run ci.yml # Run specific workflow
gh run list # List recent runs
gh run view 123456 # View specific run
gh run logs 123456 # Download run logsThe following aliases are configured in gh-config.yml:
gh co→gh pr checkout- Checkout pull requestgh pv→gh pr view- View pull requestgh rv→gh repo view- View repositorygh rl→gh release list- List releasesgh rc→gh release create- Create releasegh il→gh issue list- List issuesgh ic→gh issue create- Create issuegh wl→gh workflow list- List workflowsgh wr→gh run list- List workflow runs
GitHub CLI supports multiple authentication methods:
-
Personal Access Token (recommended for command line):
make gh-setup # Choose option 1 and follow the promptsCreating a Personal Access Token:
- Go to: https://github.com/settings/tokens
- Click "Generate new token" → "Generate new token (classic)"
- Select scopes:
repo(full repository access)workflow(GitHub Actions)admin:org(if organization repository)
- Copy the token and use it in the setup script
-
Web Browser:
gh auth login --web
-
SSH Key:
gh auth login --git-protocol ssh
The GitHub CLI is integrated with the project's release process:
# Standard release workflow
make version # Update version if needed
make test # Run all tests
make build-prod # Create production build
make gh-release # Create GitHub release with build artifact# Check authentication status
gh auth status
# Re-authenticate if needed
gh auth logout
make gh-setup# Verify repository access
gh repo view
# Check if you have write access
gh api repos/:owner/:repo --jq .permissions# Check rate limit status
gh api rate_limitGitHub CLI uses authenticated requests (5,000/hour) vs unauthenticated (60/hour), so authentication is strongly recommended.