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

# GitHub

> Read repository, community, and collaboration data from a GitHub organization

The GitHub source reads repositories, stars, watchers, and collaboration data
for one organization. It is built with an
[HTTP manifest](/pages/connectors/building-a-connector/http-manifests) and is
**beta**. Its resources are stable, though future releases may add columns.
It targets API version `2022-11-28`.

## Configuration

| Field | Scope | Default | Description |
| - | - | - | - |
| `token` | Connection | | Required. Secret. Personal access token or GitHub App installation token. |
| `organization` | Connection | | Required. GitHub organization login. |

## Resources

`repositories` lists all repositories in the organization. For every
repository, Filament then requests its issues and pull requests and adds the
repository name to each row. Both include open and closed items. GitHub's
issues endpoint also returns pull requests, so issue rows retain a
`pull_request` marker that lets you distinguish them.

Additional resources cover comments, reactions, releases, code, members, teams,
Actions, deployments, traffic, statistics, Projects, security, and Discussions.
Only selected resources are emitted; their parents are scanned as needed.
The picker defaults to repositories, repository details, star history, forks,
issues, pull requests, issue and review comments, labels, milestones,
contributors, and languages. All other resources are opt-in.
`stargazers` includes `starred_at`. Actual watchers are subscribers, counted by
`repository_details.subscribers_count`; GitHub's `watchers_count` counts stars.

## Modes

All resources support full reads. If interrupted, a full read of a top-level
resource resumes after its last completed page.

`issues`, `issue_comments`, and `pull_request_review_comments` support
incremental reads:

| | |
| - | - |
| Cursor field | `updated_at` |
| Request parameter | `since` (query) |
| Comparator | `time` |
| Checkpoint key | `<resource>_updated_at` |
| Overlap | 300 seconds |

The cursor field is fixed by the manifest. Only a lookback window is
user-configurable, and only because the comparator is `time`. Each resource
shares a single durable watermark across repositories. The 300-second overlap
re-reads a window to cover repositories that changed during the scan.
All other resources are read in full.

Use full replace for current membership such as stars and watchers, and for
keyless `issue_timeline` rows. Use full upsert for `traffic_views` and
`traffic_clones` to retain history beyond GitHub's 14-day window.

## Behavior

* **Auth**: bearer token from `token` on every request, with read permissions
  for selected resources. Teams require Organization Members read access; star
  and watcher identities require repository admin or collaborator access.
  Restricted identity listings can be empty.
* **Pagination**: RFC 5988 `Link` headers (`rel="next"`), with `per_page=100`
  set as a default query parameter. Star history uses 30; Discussions use
  GraphQL cursors.
* **API version**: pinned via `X-GitHub-Api-Version: 2022-11-28`, so response
  fields do not change with GitHub's rolling default.
* **Rate limiting**: one request per second, with manifest-defined throttling
  rules honoring `Retry-After` and configured budget-reset headers.
* **Statistics**: pending responses are retried; results preserve their native
  JSON shape. GitHub's endpoint-specific history and size limits still apply.
* Every resource carries a `raw` remainder column preserving fields the
  manifest does not project.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.