claude-code - 💡(How to fix) Fix [BUG] GitHub Enterprise Server repositories stay empty [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56282Fetched 2026-05-06 06:32:17
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

Code Example

Unable to use cloud environments due to missing repository data
Webhook payload sample:

---

The webhook is being accepted but the repository data isn't appearing in the API response, preventing us from using Cloud environments and potential automations with our GHES instance.

### What Should Happen?

We should be able to select our repositories. This does work for other similar tools that have the GitHub Enterprise Server intergration (Cursor, etc).

### Error Messages/Logs
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Issue: GitHub Enterprise Server webhook processing failure

GHES successfully connected via custom OAuth app Webhook fired successfully with 140+ repositories in the payload Webhook returns {"status":"success"} (HTTP 200) API endpoint https://claude.ai/api/organizations/{organization_id}/code/repos?ghe_configuration_id={id} returns empty: {"repos": [], "sso_required_org_ids": null, "sso_required_orgs": null, "sso_authorize_url": null} Unable to use cloud environments due to missing repository data Webhook payload sample:

"repositories_added": [
  {
    "id": 12345,
    "node_id": "R_kgDOAFzbdA",
    "name": "name",
    "full_name": "name",
    "private": true
  },
  // ... 140+ more repositories
]

The webhook is being accepted but the repository data isn't appearing in the API response, preventing us from using Cloud environments and potential automations with our GHES instance.

What Should Happen?

We should be able to select our repositories. This does work for other similar tools that have the GitHub Enterprise Server intergration (Cursor, etc).

Error Messages/Logs

Everything seems to pass. Webhook returns `status: success`, etc.

Steps to Reproduce

  1. Have a GitHub Enterprise Server.
  2. Create a custom GitHub app with the required permissions.
  3. Create a custom OAuth app.
  4. Fill in the required fields in the form when creating the Server in the Claude Code settings.
  5. Go to /code, see a button that asks you to login to your GitHub Enterprise account.
  6. Succesfully login and redirect back.
  7. See 0 repositories. The endpoint that fetches this returns an empty array.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.128 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

extent analysis

TL;DR

The issue might be resolved by verifying the webhook payload processing and repository data synchronization between GitHub Enterprise Server and Claude Code API.

Guidance

  • Verify that the repositories_added payload from the webhook is correctly processed and stored in the Claude Code database.
  • Check the API endpoint https://claude.ai/api/organizations/{organization_id}/code/repos?ghe_configuration_id={id} to ensure it is querying the correct data source for repository information.
  • Investigate potential issues with data synchronization between GitHub Enterprise Server and Claude Code, such as authentication, authorization, or rate limiting.
  • Test the API endpoint with a smaller payload to see if the issue is related to the large number of repositories (140+) in the webhook payload.

Example

No code snippet is provided as the issue does not contain sufficient information about the implementation details.

Notes

The issue may be related to the specific implementation of the Claude Code API or the GitHub Enterprise Server integration, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Verify the webhook payload processing and repository data synchronization to identify the root cause of the issue, as the problem may not be directly related to the Claude Code version.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] GitHub Enterprise Server repositories stay empty [1 comments, 2 participants]