Skip to content

Add a guide for agentic access to GitHub via Beams - #69580

Open
ptgott wants to merge 1 commit into
masterfrom
paul.gottschling/2026-08-11-github
Open

Add a guide for agentic access to GitHub via Beams#69580
ptgott wants to merge 1 commit into
masterfrom
paul.gottschling/2026-08-11-github

Conversation

@ptgott

@ptgott ptgott commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Add a guide to using Beams with Teleport-protected GitHub organizations in docs/pages/beams. Unlike the database guide, this guide does not lend itself to a quick, single-purpose demo, so the guide offloads the work of setting up GitHub with Teleport to our pre-existing tutorial. This guide provides a high-level overview of the flow for using Beams with a Teleport-protected GitHub organization.

Related changes:

  • Edit guide titles: Since the GitHub guide cannot be a demo guide, edit the database guide to make the titles of the two guides consistent.
  • Also add an audit step to the database guide. The GitHub guide adds step to check audit events. Mirror this change in the database guide since it's a straightforward edit.

@ptgott ptgott added no-changelog Indicates that a PR does not require a changelog entry backport/branch/v18 no-test-plan Bypasses the test plan validation bot labels Aug 11, 2026
@github-actions

github-actions Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Amplify deployment status

Branch Commit Job ID Status Preview Updated (UTC)
paul.gottschling/2026-08-11-github e9dc9e0 2 ✅SUCCEED paul-gottschling-2026-08-11-github 2026-08-11 19:57:33

Preview links for changed docs pages

Add a guide to using Beams with Teleport-protected GitHub organizations
in `docs/pages/beams`. Unlike the database guide, this guide does not
lend itself to a quick, single-purpose demo, so the guide offloads the
work of setting up GitHub with Teleport to our pre-existing tutorial.
This guide provides a high-level overview of the flow for using Beams
with a Teleport-protected GitHub organization.

Related changes:
- Edit guide titles: Since the GitHub guide cannot be a demo guide, edit
  the database guide to make the titles of the two guides consistent.
- Also add an audit step to the database guide. The GitHub guide adds
  step to check audit events. Mirror this change in the database guide
  since it's a straightforward edit.
@ptgott
ptgott force-pushed the paul.gottschling/2026-08-11-github branch from 0317bf8 to e9dc9e0 Compare August 11, 2026 19:48
@ptgott
ptgott marked this pull request as ready for review August 11, 2026 19:56

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e9dc9e0ee7

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread docs/pages/beams/github.mdx

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should wait for the GitHub integration to ship before adding GitHub docs. Thougths?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/branch/v18 documentation no-changelog Indicates that a PR does not require a changelog entry no-test-plan Bypasses the test plan validation bot size/md

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants