Error in Create Issue Branch app configuration

[create-issue-branch]

Error in app configuration:

Exception while parsing configuration YAML: Bad credentials - https://docs.github.com/rest

Please check the syntax of your .issue-branch.yml

[traycerai]

Plan

Observations

The repository has a .github/ directory containing only release.yml and workflows/build-test.yml. There is no .github/issue-branch.yml file present. The "Create Issue Branch" GitHub App is installed on this repository and is throwing a Bad credentials error when attempting to resolve its configuration — this is a known behaviour of the app when it fails to fetch configuration (e.g., from an inaccessible org-level .github repository or due to a missing/invalid token).

Approach

The simplest and correct fix is to add a repository-level .github/issue-branch.yml configuration file. A repository-level config takes precedence over any org/user-level config, short-circuiting the API call that is producing the Bad credentials error. No secrets or tokens need to be changed.

---

Implementation Steps

1. Create .github/issue-branch.yml

Add the file file:.github/issue-branch.yml to the repository with a minimal valid configuration. For example:

# Create Issue Branch configuration
# https://github.com/robvanderleek/create-issue-branch

mode: auto
branchName: full
silent: false

• mode: auto — creates a branch when an issue is assigned (the default behaviour).
• branchName: full — uses the format issue-<number>-<title> (the default).
• silent: false — the app comments on the issue after branch creation (the default).

You can adjust these values to match your team's preferred workflow. The key requirement is that the file exists and is valid YAML so the app stops attempting to fall back to an org-level config lookup (which is what triggers the Bad credentials error).

2. Verify the fix

After merging the file, re-assign or re-open an issue to trigger the Create Issue Branch app. Confirm:

• No new "Error in Create Issue Branch app configuration" issue is opened.
• A branch is created as expected.
• Close the existing open error issue (Error in Create Issue Branch app configuration #356) once confirmed working.

Import In IDE

🤖 Prompt for AI Agents

## Observations

The repository has a `.github/` directory containing only `release.yml` and `workflows/build-test.yml`. There is **no `.github/issue-branch.yml`** file present. The "Create Issue Branch" GitHub App is installed on this repository and is throwing a `Bad credentials` error when attempting to resolve its configuration — this is a known behaviour of the app when it fails to fetch configuration (e.g., from an inaccessible org-level `.github` repository or due to a missing/invalid token).

## Approach

The simplest and correct fix is to add a repository-level `.github/issue-branch.yml` configuration file. A repository-level config takes precedence over any org/user-level config, short-circuiting the API call that is producing the `Bad credentials` error. No secrets or tokens need to be changed.

---

## Implementation Steps

### 1. Create `.github/issue-branch.yml`

Add the file `file:.github/issue-branch.yml` to the repository with a minimal valid configuration. For example:

```yaml
# Create Issue Branch configuration
# https://github.com/robvanderleek/create-issue-branch

mode: auto
branchName: full
silent: false
```

- **`mode: auto`** — creates a branch when an issue is assigned (the default behaviour).
- **`branchName: full`** — uses the format `issue-<number>-<title>` (the default).
- **`silent: false`** — the app comments on the issue after branch creation (the default).

> You can adjust these values to match your team's preferred workflow. The key requirement is that the file exists and is valid YAML so the app stops attempting to fall back to an org-level config lookup (which is what triggers the `Bad credentials` error).

### 2. Verify the fix

After merging the file, re-assign or re-open an issue to trigger the Create Issue Branch app. Confirm:
- No new "Error in Create Issue Branch app configuration" issue is opened.
- A branch is created as expected.
- Close the existing open error issue (#356) once confirmed working.

---

Execution Information

Branch: main
Commit: cb7a449

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.