github-access

name	github-access
description	Access GitHub repositories programmatically using the exe.dev GitHub integration, gh CLI, or REST API. Use when interacting with GitHub repositories, issues, pull requests, workflows, discussions, or actions. On exe.dev VMs, prefer the tokenless GitHub integration before falling back to local gh authentication or GH_TOKEN.

GitHub Access

Overview

This skill enables programmatic GitHub access through the exe.dev GitHub integration, the gh CLI, or the REST API with curl. Prefer credentials held outside the VM when exe.dev provides them.

Prerequisites and Tool Selection

Before performing GitHub operations, follow this workflow:

1. Prefer the exe.dev GitHub integration

On an exe.dev VM with gh installed, test the aggregate integration hostname:

GH_HOST=github.int.exe.xyz gh auth status --hostname github.int.exe.xyz

If this succeeds, use the integration for the rest of the task:

export GH_HOST=github.int.exe.xyz
gh repo view OWNER/REPO
gh issue list --repo OWNER/REPO

No GH_TOKEN is needed. The credential stays outside the VM and is injected at the network edge. Read references/exe-dev-integration.md for setup, repository scope, read-only mode, attribution, cloning, and pushing.

For Git operations, use the integration hostname rather than github.com:

git clone https://github.int.exe.xyz/OWNER/REPO.git
git push https://github.int.exe.xyz/OWNER/REPO.git HEAD

2. Fall back to ordinary GitHub authentication

Only when the exe.dev integration is unavailable:

1. If gh is installed and succeeds, use with its existing authentication.