From 48aa346dbe62a88c0a3d04c2b1a6752dac30fbf3 Mon Sep 17 00:00:00 2001 From: Jean-Eudes Peloye Date: Mon, 9 Feb 2026 09:35:59 +0100 Subject: [PATCH] docs: add FAQ item about bun install on GHES --- docs/configuration.md | 2 ++ docs/faq.md | 26 ++++++++++++++++++++++++++ 2 files changed, 28 insertions(+) diff --git a/docs/configuration.md b/docs/configuration.md index 46c2687c5..07e488c84 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -370,4 +370,6 @@ Use `path_to_bun_executable` to provide your own Bun runtime instead of the defa # ... other inputs ``` +> **Note for GHES users**: The automatic Bun installation requires authenticated access to github.com to avoid rate limits. On GitHub Enterprise Server, you'll need to either provide a github.com PAT to `setup-bun` or use `path_to_bun_executable`. See the [FAQ](faq.md#how-do-i-fix-bun-installation-issues-on-github-enterprise-server-ghes) for setup instructions. + **Important**: Using incompatible versions may cause the action to fail. Ensure your custom executables are compatible with the action's requirements. diff --git a/docs/faq.md b/docs/faq.md index 26af2d637..f8488e3c6 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -205,6 +205,32 @@ However, tools from these servers still need to be explicitly allowed via `claud ## Troubleshooting +### How do I fix Bun installation issues on GitHub Enterprise Server (GHES)? + +The `setup-bun` action requires authenticated access to github.com to avoid rate limits when fetching Bun releases. +On GHES, we recommend installing Bun externally and providing the path to the executable: + +```yaml +steps: + # Install Bun using the official installer + - name: Install Bun + run: | + curl -fsSL https://bun.sh/install | bash + echo "$HOME/.bun/bin" >> $GITHUB_PATH + # ... or with setup-bun and a github.com token + - name: Install Bun + uses: oven-sh/setup-bun@v2 + with: + bun-version: 1.3.6 + token: # PAT with public_repo scope for github.com + + # Use the action with custom Bun path + - uses: anthropics/claude-code-action@v1 + with: + path_to_bun_executable: "$HOME/.bun/bin/bun" + # ... other inputs +``` + ### How can I debug what Claude is doing? Check the GitHub Action log for Claude's run for the full execution trace.