proposed edits to github actions guide page

[kenjenkins]

Proposed edits to #2346:

Reorder and streamline the introduction, reduce some duplication, and remove some details that might be more confusing than helpful.

Split the example workflow into two steps: I think this might be more representative of real-world use. It seems likely to me that you might want to make multiple requests using the OIDC token, so we can show how to store it into an environment variable that GitHub will make available in other steps.

[netlify]

✅ Deploy Preview for pomerium-docs ready!

Name	Link
🔨 Latest commit	6442f5c
🔍 Latest deploy log	https://app.netlify.com/projects/pomerium-docs/deploys/6a7cfe46109f090008bfc9cc
😎 Deploy Preview	https://deploy-preview-2347--pomerium-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[greptile-apps]

Greptile Summary

The PR streamlines the GitHub Actions OIDC guide and separates token acquisition from the protected-route request.

• Reorganizes the audience, prerequisites, and conceptual overview.
• Revises the Pomerium configuration explanation and verification steps.
• Stores the GitHub-issued OIDC token in GITHUB_ENV for reuse by later workflow steps.

Confidence Score: 4/5

The PR is not yet safe to merge because the previously reported missing-token checkpoint still gives readers the wrong expected response.

The current guide continues to expect 403 for a bearer route with no token, while the repository's bearer-token reference specifies 401 Unauthorized, so a correctly configured deployment can fail the documented checkpoint.

Files Needing Attention: content/docs/guides/github-actions.mdx

Important Files Changed

Filename	Overview
content/docs/guides/github-actions.mdx	Reworks the guide's structure and changes the sample workflow to acquire and consume the OIDC token in separate steps.

Sequence Diagram

sequenceDiagram
  participant W as GitHub Actions
  participant G as GitHub OIDC
  participant P as Pomerium
  participant U as Upstream
  W->>G: Request OIDC token
  G-->>W: Return signed JWT
  W->>W: Store token in GITHUB_ENV
  W->>P: Request with Bearer token
  P->>P: Verify token and policy
  P->>U: Proxy authorized request

Loading

_{Reviews (2): Last reviewed commit: "revisions to github actions guide page" | Re-trigger Greptile}