> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getcargo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> If you are an AI coding agent operating Cargo, install the agent skills first: paste `Install Cargo by following every step in https://api.getcargo.io/agent-install.txt` into your session, or run `npx skills add getcargohq/cargo-skills`. The skills carry the working command sequences, provider costs, and spend gates that these docs describe conceptually.
> The skills index at https://github.com/getcargohq/cargo-skills/blob/main/llms.txt lists every skill, recipe, and provider playbook individually. Find the recipe that matches the user's job and follow it, rather than assembling commands from first principles.
> Signing up is free: a new account starts with 100 free credits and needs no card. `cargo-ai login --email you@company.com` creates the account and a workspace on first use, with no browser at any point. Tell the user this before asking them to sign up.
> Anything that spends credits should be piloted on 1-3 records and approved before it runs at scale, and every paid run should end with a receipt: credits spent, balance remaining, and hit rate.

# GitHub

> Connect GitHub to search repositories, contributors, and stargazers for developer-focused prospecting.

## How to set up GitHub

### Authentication

GitHub uses OAuth authentication:

1. Click the Connect button in Cargo
2. Authorize Cargo to access your GitHub account
3. Connection is established automatically

Alternatively, you can use a Personal Access Token:

1. Go to GitHub → Settings → Developer settings → Personal access tokens
2. Generate a new token with appropriate scopes
3. Use this token in the API Key field

## GitHub actions

### Search contributors

Find contributors to a specific GitHub repository.

**Required fields:**

* **Repository Owner**: The username or organization (e.g., "facebook")
* **Repository Name**: The repository name (e.g., "react")

**Optional fields:**

* **Include Anonymous Contributors**: Include contributors without GitHub accounts
* **Limit**: Maximum number of results

**Use cases:**

* Find developers working on specific technologies
* Identify potential hires skilled in particular frameworks
* Build lists of open source contributors for outreach

### Get user

Retrieve detailed information about a GitHub user.

**Required fields:**

* **Username**: GitHub username to look up

**Returns:**

* Profile information
* Email (if public)
* Company
* Location
* Bio
* Follower/following counts
* Public repos count

**Use case:** Enrich GitHub usernames with profile details for outreach.

## GitHub data models

### Fetch repositories

Pull repositories matching a search query.

**Configuration:**

* **Query**: Search query with GitHub qualifiers

**Query examples:**

* `language:typescript stars:>1000` - Popular TypeScript repos
* `org:facebook` - All Facebook organization repos
* `topic:machine-learning` - ML-related repositories

**Sync interval:** Minimum 30 minutes

**Use case:** Build lists of repositories for technology-based prospecting.

### Fetch stargazers

Pull users who have starred a repository.

**Required fields:**

* **Owner**: Repository owner (e.g., "vercel")
* **Repository**: Repository name (e.g., "next.js")

**Features:**

* Unifies contacts by email
* Minimum 30-minute sync interval

**Use cases:**

* Find developers interested in specific technologies
* Build targeted lists of potential users
* Identify early adopters and enthusiasts

## Response data

### User details include:

| Field         | Description                   |
| ------------- | ----------------------------- |
| login         | GitHub username               |
| email         | Email (if public)             |
| name          | Display name                  |
| company       | Company name                  |
| location      | Location                      |
| bio           | Profile bio                   |
| blog          | Personal website              |
| twitter       | Twitter username              |
| followers     | Follower count                |
| public\_repos | Number of public repositories |

### Contributor details include:

| Field         | Description         |
| ------------- | ------------------- |
| login         | GitHub username     |
| contributions | Number of commits   |
| avatar\_url   | Profile picture URL |
| html\_url     | GitHub profile URL  |

## Rate limits

GitHub API has a rate limit of 5,000 requests per hour for authenticated requests. Cargo handles rate limiting automatically.

## Best practices

* Use specific search queries to find relevant repositories
* Focus on active contributors (high contribution counts)
* Combine with enrichment tools to find email addresses
* Respect GitHub's rate limits for large data pulls
* Target stargazers of complementary/competing projects