github-auth

To set up GitHub authentication, the system detects existing credentials via `gh auth status`, git credential storage, or environment tokens, then configures HTTPS personal access tokens or SSH keys for repository operations. It automatically determines the best available auth method for your environment.

Yes, GitHub API access works without the `gh` CLI by using a personal access token from environment variables or git credential helpers. The system enables token-based API requests and git push permissions without requiring `gh` to be installed.

GitHub authentication works in CI-like environments using a git-only workflow with environment tokens like `GITHUB_TOKEN` or stored git credentials. It requires no sudo access and configures git credential helpers directly for automated repository operations.

Configuring SSH keys for GitHub involves secure key handling and detection of existing authentication methods. The system supports SSH keys alongside HTTPS personal access tokens, automatically selecting the appropriate credential type for your git push and pull request workflows.

GitHub authentication with environment tokens fails when the `GITHUB_TOKEN` lacks proper scopes for git push permissions or API requests. The system requires tokens with correct scopes and can fall back to `gh auth status` or git credential storage if environment tokens are insufficient.

You do not need the `gh` CLI to manage GitHub pull requests and issues, as token-based API access handles these workflows. However, installing `gh` provides richer authentication and workflow capabilities compared to the git-only path.