Skip to content

[CXH-3498] - Docs: baton-github — add "when to use" guidance and document missing capabilities - #196

Open
sergiocorral-conductorone wants to merge 4 commits into
mainfrom
sergiocorral/cxh-3498-docs-baton-github-when-to-use
Open

sergiocorral-conductorone wants to merge 4 commits into
mainfrom
sergiocorral/cxh-3498-docs-baton-github-when-to-use

Conversation

@sergiocorral-conductorone

@sergiocorral-conductorone sergiocorral-conductorone commented Oct 27, 2026 •

Copy link
Copy Markdown

INTENT

  • Replace the "custom domain" note at the top of docs/connector.mdx with when-to-use guidance: github.com orgs, one org per GitHub App or several orgs with one PAT, the only GitHub connector with fine-grained PAT support, and a link to the shared "Choose a GitHub connector" guide.
  • Add org_role (sync + provision) to the Capabilities table; no enterprise roles, licenses, or last-activity.
  • Document account provisioning behavior for EMU orgs and point to the IdP's GitHub SCIM integration.

What changed

docs/connector.mdx only: rewritten top note (links /baton/choose-github-connector; the custom-domain pointer to GitHub Enterprise is removed because the guide covers GHES and GHEC routing), new "Org roles" capability row, new EMU note under the provisioning paragraph.

Verified in code

  • org_role sync + provision: baton_capabilities.json (org_role entry), pkg/connector/org_role.go (Grants, Grant, Revoke)
  • Account provisioning sends an org invitation: pkg/connector/invitation.go (CreateAccount -> CreateOrgInvitation)
  • EMU error ("accounts are provisioned by the IdP, not via org invitations"): pkg/connector/invitation.go (isEMUOrgError)
  • PAT (token), GitHub App (app-id, org), multi-org (orgs): config_schema.json
  • Fine-grained PAT: already documented in the connector page as an auth option. It is unique to this connector: GitHub Enterprise documents only classic PAT and GitHub App auth, and GitHub Enterprise Cloud's config accepts only a GitHub App (enterprise-slug, app-id, app-privatekey-path, installation-id).

Open items

Fixes CXH-3498

🤖 Generated with AI

@linear-code

linear-code Bot commented Oct 27, 2026

Copy link
Copy Markdown

CXH-3498

@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor
Superseded — see the current review report for commit 568c553c7b82

Connector PR Review: [CXH-3498] - Docs: baton-github — add "when to use" guidance and document missing capabilities

Blocking Issues: 0 | Suggestions: 1 | Threads Resolved: 0
Criteria: Criteria status: loaded .claude/skills/ci-review.md from trusted base 2c5bd7f375ec.
Review mode: full
View review run

Review Summary

This PR changes only docs/connector.mdx. It rewrites the top Tip with "when to use" guidance, adds an "Org roles" row (sync + provision) to the Capabilities table, and adds a Note on Enterprise Managed Users (EMU) under the account-provisioning paragraph. I scanned the full PR diff for security and correctness issues. No code, config, or dependency files changed.

Each documentation claim was checked against the code:

  • Org roles: org_role is listed with CAPABILITY_SYNC,CAPABILITY_PROVISION in baton_capabilities.json.
  • EMU error: isEMUOrgError in pkg/connector/invitation.go:290-291,495 produces the "provisioned by the IdP" error.
  • Auth and orgs: config_schema.json has the single org field for a GitHub App and the multi-value orgs field for a personal access token.
  • Fine-grained tokens: they are already documented as Option 2 in the same file.

The trusted repo-local criteria were applied. The Documentation Staleness checks (D1–D4) and the breaking-change gate (BP3) are the relevant ones, and they produced the one suggestion below. The code-level sections (log levels, error wrapping, spans, JSON types, provisioning, sync data loss) do not apply because no Go code changed.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

  • New: docs/connector.mdx:23: the Capabilities table still leaves out enterprise roles. The connector registers an enterprise_role resource type with a provisioning builder (pkg/connector/connector.go:92,160), and the enterprises config field describes syncing and provisioning it. The PR body says "no enterprise roles" without explaining why. Either add a row (noting it needs the enterprises config) or explain why it is left out. Confidence: medium.
Prompt for AI agents
Verify each finding against the current code and only fix it if needed.

## Suggestions

In `docs/connector.mdx`:
- Around line 18-26 (Capabilities table): The connector has an `enterprise_role` resource type (pkg/connector/connector.go:92) with sync and provisioning (EnterpriseRoleProvisioningBuilder), enabled through the `enterprises` config field. Add an "Enterprise roles" row with sync and provision checkmarks, plus a short note that it needs the `enterprises` config and enterprise admin rights (a GitHub App only syncs/provisions the built-in Owner role). If leaving it out is deliberate, say why in the PR description.

Comment thread docs/connector.mdx Resolved
@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor
Superseded — see the current review report for commit 7abb6c5274b9

Connector PR Review: [CXH-3498] - Docs: baton-github — add "when to use" guidance and document missing capabilities

Blocking Issues: 0 | Suggestions: 1 | Threads Resolved: 0
Criteria: Criteria status: loaded .claude/skills/ci-review.md from trusted base 2c5bd7f375ec.
Review mode: full
View review run

Review Summary

This PR changes only docs/connector.mdx. It rewrites the top Tip with "when to use" guidance, adds an "Org roles" row (sync + provision) to the Capabilities table, and adds a Note on Enterprise Managed Users (EMU) under the account-provisioning paragraph. I scanned the full PR diff for security and correctness issues. No code, config, or dependency files changed.

Each documentation claim was checked against the code:

  • Org roles: org_role is listed with CAPABILITY_SYNC,CAPABILITY_PROVISION in baton_capabilities.json.
  • EMU error: isEMUOrgError in pkg/connector/invitation.go:290-291,495 produces the "provisioned by the IdP" error.
  • Auth and orgs: config_schema.json has the single org field for a GitHub App and the multi-value orgs field for a personal access token.
  • Fine-grained tokens: they are already documented as Option 2 in the same file.

The trusted repo-local criteria were applied. The Documentation Staleness checks (D1–D4) and the breaking-change gate (BP3) are the relevant ones, and they produced the one suggestion below. The code-level sections (log levels, error wrapping, spans, JSON types, provisioning, sync data loss) do not apply because no Go code changed.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

  • New: docs/connector.mdx:23: the Capabilities table still leaves out enterprise roles. The connector registers an enterprise_role resource type with a provisioning builder (pkg/connector/connector.go:92,160), and the enterprises config field describes syncing and provisioning it. The PR body says "no enterprise roles" without explaining why. Either add a row (noting it needs the enterprises config) or explain why it is left out. Confidence: medium.
Prompt for AI agents
Verify each finding against the current code and only fix it if needed.

## Suggestions

In `docs/connector.mdx`:
- Around line 18-26 (Capabilities table): The connector has an `enterprise_role` resource type (pkg/connector/connector.go:92) with sync and provisioning (EnterpriseRoleProvisioningBuilder), enabled through the `enterprises` config field. Add an "Enterprise roles" row with sync and provision checkmarks, plus a short note that it needs the `enterprises` config and enterprise admin rights (a GitHub App only syncs/provisions the built-in Owner role). If leaving it out is deliberate, say why in the PR description.

Reviewed commit: 568c553c7b82

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

No blocking issues found — see the full review report

@luisina-santos luisina-santos left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Holding this until the shared "Choose a GitHub connector" guide from CXH-3497 exists. That guide isn't written yet, and the parent issue requires all three connector pages to link it.

Once the guide is published, add the link to the note at the top of each page and merge these three PRs together:

Comment thread docs/connector.mdx Resolved
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor
Superseded — see the current review report for commit 7abb6c5274b9

Connector PR Review: [CXH-3498] - Docs: baton-github — add "when to use" guidance and document missing capabilities

Blocking Issues: 0 | Suggestions: 1 | Threads Resolved: 0
Criteria: Criteria status: loaded .claude/skills/ci-review.md from trusted base 94ffb800433b.
Review mode: full
View review run

Review Summary

This PR only changes docs/connector.mdx. It replaces the custom-domain/GitHub Enterprise note at the top with "when to use" guidance and a link to a "Choose a GitHub connector" guide. It also adds an "Org roles" row (sync + provision) to the Capabilities table, and a note that account provisioning fails for EMU orgs, pointing to the IdP's SCIM integration. I scanned the full diff for security and correctness and checked the doc claims against the code:

  • isEMUOrgError and the "provisioned by the IdP" error are at pkg/connector/invitation.go:290-291.
  • The org, orgs, and instance-url fields are in config_schema.json.
  • Fine-grained PAT setup is already documented in this page.

The trusted repo-local criteria loaded. Its documentation-staleness and breaking-change rules apply to this docs-only PR; it doesn't touch code, endpoints, logging, or sync paths, so the connector code rules (R/S/L/P) don't apply.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

  • New docs/connector.mdx:12: The PR description doesn't match the diff.
    • The description says the "Choose a GitHub connector" guide has no URL yet and that "no link or placeholder is in the mdx". The latest commit adds a link to /baton/choose-github-connector anyway. If that page isn't published, this is a dead link, and it replaces the only pointer to the GitHub Enterprise (/baton/github-enterprise) integration for custom-domain users.
    • The line also says this is "the only GitHub connector that supports fine-grained personal access tokens", which the description lists as "Not asserted in the docs".
    • Confidence: medium.

Resolved prior findings

  • docs/connector.mdx:23 (enterprise roles missing from the Capabilities table): fixed as far as this suggestion goes. It asked the author either to add the row or to explain the omission in the PR description. The description now records that leaving out enterprise_role is deliberate (CXH-3498 limits the page to customer-facing capabilities, and enterprise roles need the enterprises config), and a person resolved the thread.
Prompt for AI agents
Verify each finding against the current code and only fix it if needed.

## Suggestions

In `docs/connector.mdx`:
- Around line 12: The top note links to `/baton/choose-github-connector`, but the PR description says that guide isn't published yet and that no link was added. The note also says this is "the only GitHub connector that supports fine-grained personal access tokens", which the description says is not asserted. Confirm the guide page exists before merging; if it doesn't, keep the earlier sentence pointing custom-domain users to `/baton/github-enterprise` until it does. Remove the exclusivity claim or verify it. Then update the PR description to match what the docs say.

Comment thread docs/connector.mdx Resolved
@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor
Superseded — see the current review report for commit 13387923bf8e

Connector PR Review: [CXH-3498] - Docs: baton-github — add "when to use" guidance and document missing capabilities

Blocking Issues: 0 | Suggestions: 1 | Threads Resolved: 0
Criteria: Criteria status: loaded .claude/skills/ci-review.md from trusted base 94ffb800433b.
Review mode: full
View review run

Review Summary

This PR only changes docs/connector.mdx. It replaces the custom-domain/GitHub Enterprise note at the top with "when to use" guidance and a link to a "Choose a GitHub connector" guide. It also adds an "Org roles" row (sync + provision) to the Capabilities table, and a note that account provisioning fails for EMU orgs, pointing to the IdP's SCIM integration. I scanned the full diff for security and correctness and checked the doc claims against the code:

  • isEMUOrgError and the "provisioned by the IdP" error are at pkg/connector/invitation.go:290-291.
  • The org, orgs, and instance-url fields are in config_schema.json.
  • Fine-grained PAT setup is already documented in this page.

The trusted repo-local criteria loaded. Its documentation-staleness and breaking-change rules apply to this docs-only PR; it doesn't touch code, endpoints, logging, or sync paths, so the connector code rules (R/S/L/P) don't apply.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

  • New docs/connector.mdx:12: The PR description doesn't match the diff.
    • The description says the "Choose a GitHub connector" guide has no URL yet and that "no link or placeholder is in the mdx". The latest commit adds a link to /baton/choose-github-connector anyway. If that page isn't published, this is a dead link, and it replaces the only pointer to the GitHub Enterprise (/baton/github-enterprise) integration for custom-domain users.
    • The line also says this is "the only GitHub connector that supports fine-grained personal access tokens", which the description lists as "Not asserted in the docs".
    • Confidence: medium.

Resolved prior findings

  • docs/connector.mdx:23 (enterprise roles missing from the Capabilities table): fixed as far as this suggestion goes. It asked the author either to add the row or to explain the omission in the PR description. The description now records that leaving out enterprise_role is deliberate (CXH-3498 limits the page to customer-facing capabilities, and enterprise roles need the enterprises config), and a person resolved the thread.
Prompt for AI agents
Verify each finding against the current code and only fix it if needed.

## Suggestions

In `docs/connector.mdx`:
- Around line 12: The top note links to `/baton/choose-github-connector`, but the PR description says that guide isn't published yet and that no link was added. The note also says this is "the only GitHub connector that supports fine-grained personal access tokens", which the description says is not asserted. Confirm the guide page exists before merging; if it doesn't, keep the earlier sentence pointing custom-domain users to `/baton/github-enterprise` until it does. Remove the exclusivity claim or verify it. Then update the PR description to match what the docs say.

Reviewed commit: 7abb6c5274b9

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

No blocking issues found — see the full review report

@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor
Superseded — see the current review report for commit 13387923bf8e

Connector PR Review: [CXH-3498] - Docs: baton-github — add "when to use" guidance and document missing capabilities

Blocking Issues: 0 | Suggestions: 0 | Threads Resolved: 0
Criteria: Criteria status: loaded .claude/skills/ci-review.md from trusted base 94ffb800433b.
Review mode: incremental since 7abb6c5
View review run

Review Summary

The PR changes only docs/connector.mdx. It rewrites the top "when to use" note, adds an Org roles row (sync and provision) to the Capabilities table, and adds an EMU note about account provisioning. The new commit removes the claim that this is the "only GitHub connector" supporting fine-grained PATs and puts back the custom-domain pointer to /baton/github-enterprise. The PR description now matches the diff.

I scanned the full PR diff for security and correctness issues and checked each docs claim against the code:

  • Org roles: org_role has Grants, Grant and Revoke in pkg/connector/org_role.go:137,303,394 and an entry in baton_capabilities.json.
  • EMU note: isEMUOrgError matches a 422 response whose message contains "managed by an enterprise". CreateAccount then returns the "provisioned by the IdP" error (pkg/connector/invitation.go:290-291,495), so the note describes real behavior.
  • Fine-grained PATs: already covered later on the page (Option 2).

The trusted repo-local criteria loaded. Their code-focused sections (logging, error wrapping, spans, JSON types, provisioning, sync data loss) don't apply to a docs-only change. Under the breaking-change and doc-staleness rules, these updates make the capability docs more accurate, and nothing breaks. No code, config or go.mod changed. I found no coverage gaps.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

None.

Resolved prior findings

  • Mismatch between the description and the top note (dead-link / exclusivity thread, now outdated): fixed.
    • docs/connector.mdx:12 no longer claims exclusive fine-grained PAT support.
    • The same line links custom-domain users to /baton/github-enterprise again.
    • The PR description now says plainly that the /baton/choose-github-connector guide (CXH-3497) isn't published yet, and that the link stays in place until it goes live.
    • Someone still needs to confirm that guide is published before or with this docs release. The author has listed that as an open item, so it doesn't count as a finding.
  • Enterprise roles missing from the Capabilities table (docs/connector.mdx:23): fixed.
    • The finding asked for either a table row or a stated reason for leaving it out. The description gives the reason: leaving out enterprise_role is deliberate under CXH-3498's scope.
    • A person resolved the thread.

@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor
Superseded — see the current review report for commit ec15c7775d44

Connector PR Review: [CXH-3498] - Docs: baton-github — add "when to use" guidance and document missing capabilities

Blocking Issues: 0 | Suggestions: 0 | Threads Resolved: 0
Criteria: Criteria status: loaded .claude/skills/ci-review.md from trusted base 94ffb800433b.
Review mode: incremental since 7abb6c5
View review run

Review Summary

The PR changes only docs/connector.mdx. It rewrites the top "when to use" note, adds an Org roles row (sync and provision) to the Capabilities table, and adds an EMU note about account provisioning. The new commit removes the claim that this is the "only GitHub connector" supporting fine-grained PATs and puts back the custom-domain pointer to /baton/github-enterprise. The PR description now matches the diff.

I scanned the full PR diff for security and correctness issues and checked each docs claim against the code:

  • Org roles: org_role has Grants, Grant and Revoke in pkg/connector/org_role.go:137,303,394 and an entry in baton_capabilities.json.
  • EMU note: isEMUOrgError matches a 422 response whose message contains "managed by an enterprise". CreateAccount then returns the "provisioned by the IdP" error (pkg/connector/invitation.go:290-291,495), so the note describes real behavior.
  • Fine-grained PATs: already covered later on the page (Option 2).

The trusted repo-local criteria loaded. Their code-focused sections (logging, error wrapping, spans, JSON types, provisioning, sync data loss) don't apply to a docs-only change. Under the breaking-change and doc-staleness rules, these updates make the capability docs more accurate, and nothing breaks. No code, config or go.mod changed. I found no coverage gaps.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

None.

Resolved prior findings

  • Mismatch between the description and the top note (dead-link / exclusivity thread, now outdated): fixed.
    • docs/connector.mdx:12 no longer claims exclusive fine-grained PAT support.
    • The same line links custom-domain users to /baton/github-enterprise again.
    • The PR description now says plainly that the /baton/choose-github-connector guide (CXH-3497) isn't published yet, and that the link stays in place until it goes live.
    • Someone still needs to confirm that guide is published before or with this docs release. The author has listed that as an open item, so it doesn't count as a finding.
  • Enterprise roles missing from the Capabilities table (docs/connector.mdx:23): fixed.
    • The finding asked for either a table row or a stated reason for leaving it out. The description gives the reason: leaving out enterprise_role is deliberate under CXH-3498's scope.
    • A person resolved the thread.

Reviewed commit: 13387923bf8e

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

No blocking issues found — see the full review report

…or guide

GitHub Enterprise documents only classic PAT and GitHub App auth, and
GitHub Enterprise Cloud accepts only a GitHub App, so fine-grained PAT
support is unique to this connector. The custom-domain pointer is
replaced by the Choose a GitHub connector guide, which covers GHES and
GHEC routing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor
Superseded — see the current review report for commit ec15c7775d44

Connector PR Review: [CXH-3498] - Docs: baton-github — add "when to use" guidance and document missing capabilities

Blocking Issues: 0 | Suggestions: 2 | Threads Resolved: 0
Criteria: Criteria status: loaded .claude/skills/ci-review.md from trusted base 94ffb800433b.
Review mode: incremental since 1338792
View review run

Review Summary

The PR changes only docs/connector.mdx. It rewrites the top Tip with when-to-use guidance, adds an "Org roles" row (sync + provision) to the Capabilities table, and adds an EMU note about account provisioning. The new commit (ec15c77) rewrites line 12 in two ways: it now says this is the only GitHub connector that supports fine-grained PATs, and it removes the GitHub Enterprise link for custom-domain users, so the comparison guide is now the only route. I scanned the full PR diff for security and correctness. I applied the trusted repo-local criteria (docs staleness and capability accuracy checks); the code-level rules (logging, S/R7 data loss, provisioning, JSON) don't apply because no Go code changed. The incremental diff was complete, with no dropped paths or truncation.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

  • New — docs/connector.mdx:12: Custom-domain users lost their working link. The /baton/github-enterprise link was removed, so /baton/choose-github-connector is now their only path, and the PR description says that route returns 404 until CXH-3497 is published. The description also still says "The link to GitHub Enterprise for custom-domain users is kept", which no longer matches the diff.
  • New — docs/connector.mdx:12: The new text says "It's the only GitHub connector that supports fine-grained personal access tokens", but the PR description says the docs do not make that claim because this repo can't verify it. The claim needs verifying, or the description needs to match the docs.

Resolved prior findings

  • docs/connector.mdx:12 (guide link vs. description mismatch): fixed. The PR description now says the /baton/choose-github-connector link points to the unpublished CXH-3497 guide and stays in place until it goes live. The related new issue above comes from this commit removing the fallback Enterprise link.
  • docs/connector.mdx:23 (no enterprise roles row): fixed. The PR description records a deliberate decision to leave out enterprise_role under CXH-3498's scope, which is the stated reason the finding asked for.
Prompt for AI agents
Verify each finding against the current code and only fix it if needed.

## Suggestions

In `docs/connector.mdx`:
- Around line 12: The sentence pointing custom-domain users to the GitHub Enterprise integration was removed, so their only route is now the Choose a GitHub connector guide (/baton/choose-github-connector), and the PR description says that guide is still unpublished (404). Restore a sentence such as "If you use a custom domain, follow the instructions to set up the [GitHub Enterprise](/baton/github-enterprise) integration." at least until the guide is live, or update the PR description, which still says the link is kept.
- Around line 12: "It's the only GitHub connector that supports fine-grained personal access tokens" contradicts the PR description, which says the exclusivity claim is not made because it can't be verified in this repo. Either confirm the claim against the other GitHub connectors' docs and update the PR description, or go back to neutral wording such as "It also supports fine-grained personal access tokens for authentication."

Comment thread docs/connector.mdx Resolved
@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Connector PR Review: [CXH-3498] - Docs: baton-github — add "when to use" guidance and document missing capabilities

Blocking Issues: 0 | Suggestions: 2 | Threads Resolved: 0
Criteria: Criteria status: loaded .claude/skills/ci-review.md from trusted base 94ffb800433b.
Review mode: incremental since 1338792
View review run

Review Summary

The PR changes only docs/connector.mdx. It rewrites the top Tip with when-to-use guidance, adds an "Org roles" row (sync + provision) to the Capabilities table, and adds an EMU note about account provisioning. The new commit (ec15c77) rewrites line 12 in two ways: it now says this is the only GitHub connector that supports fine-grained PATs, and it removes the GitHub Enterprise link for custom-domain users, so the comparison guide is now the only route. I scanned the full PR diff for security and correctness. I applied the trusted repo-local criteria (docs staleness and capability accuracy checks); the code-level rules (logging, S/R7 data loss, provisioning, JSON) don't apply because no Go code changed. The incremental diff was complete, with no dropped paths or truncation.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

  • New — docs/connector.mdx:12: Custom-domain users lost their working link. The /baton/github-enterprise link was removed, so /baton/choose-github-connector is now their only path, and the PR description says that route returns 404 until CXH-3497 is published. The description also still says "The link to GitHub Enterprise for custom-domain users is kept", which no longer matches the diff.
  • New — docs/connector.mdx:12: The new text says "It's the only GitHub connector that supports fine-grained personal access tokens", but the PR description says the docs do not make that claim because this repo can't verify it. The claim needs verifying, or the description needs to match the docs.

Resolved prior findings

  • docs/connector.mdx:12 (guide link vs. description mismatch): fixed. The PR description now says the /baton/choose-github-connector link points to the unpublished CXH-3497 guide and stays in place until it goes live. The related new issue above comes from this commit removing the fallback Enterprise link.
  • docs/connector.mdx:23 (no enterprise roles row): fixed. The PR description records a deliberate decision to leave out enterprise_role under CXH-3498's scope, which is the stated reason the finding asked for.
Prompt for AI agents
Verify each finding against the current code and only fix it if needed.

## Suggestions

In `docs/connector.mdx`:
- Around line 12: The sentence pointing custom-domain users to the GitHub Enterprise integration was removed, so their only route is now the Choose a GitHub connector guide (/baton/choose-github-connector), and the PR description says that guide is still unpublished (404). Restore a sentence such as "If you use a custom domain, follow the instructions to set up the [GitHub Enterprise](/baton/github-enterprise) integration." at least until the guide is live, or update the PR description, which still says the link is kept.
- Around line 12: "It's the only GitHub connector that supports fine-grained personal access tokens" contradicts the PR description, which says the exclusivity claim is not made because it can't be verified in this repo. Either confirm the claim against the other GitHub connectors' docs and update the PR description, or go back to neutral wording such as "It also supports fine-grained personal access tokens for authentication."

Reviewed commit: ec15c7775d44

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

No blocking issues found — see the full review report

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants