Skip to content

docs(connectors): GitHub asset connector reference#15291

Open
devGregA wants to merge 1 commit into
bugfixfrom
github-asset-connector-docs
Open

docs(connectors): GitHub asset connector reference#15291
devGregA wants to merge 1 commit into
bugfixfrom
github-asset-connector-docs

Conversation

@devGregA

Copy link
Copy Markdown
Contributor

Adds a tool-reference entry for the GitHub asset connector, which was previously undocumented (surfaced by a customer asking what data it pulls and which token permissions it needs).

The GitHub asset connector imports GitHub repositories as Assets (Products) via the GitHub GraphQL API, reading repository metadata only (name, description, URL, owner). It is distinct from the existing GitHub Advanced Security connector, which imports code scanning / Dependabot / secret scanning alerts as findings — the two are independent and can run together.

The new section documents:

  • what data is imported and how repositories map to Assets / Organizations
  • the low-privilege token permissions required (fine-grained: Metadata: Read-only; classic: repo/public_repo + read:org)
  • that only GitHub.com / Enterprise Cloud is supported (not Enterprise Server)

Placed alphabetically, immediately before the GitHub Advanced Security entry.

🤖 Generated with Claude Code

Adds a tool-reference entry for the GitHub asset connector, which imports GitHub repositories as Assets via the GitHub GraphQL API (repository metadata only). Distinguishes it from the existing GitHub Advanced Security connector, which imports security alerts as findings.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant