Troubleshooting issues for Amazon Q Developer for GitHub
Amazon Q Developer for GitHub: end of support
On January 30, 2027, AWS will discontinue support for the Amazon Q Developer for GitHub App. New app installations will no longer be available starting November 18, 2026.
For capabilities similar to the Amazon Q Developer for GitHub App, explore Kiro and the Kiro GitHub App to access the latest models and features, including agentic coding, chat and MCP support. For more information, see Kiro GitHub App on the Kiro website
For more information about the end of support, see Amazon Q Developer end-of-support announcement
Consult the following section to troubleshoot common problems when using Amazon Q Developer for GitHub.
Amazon Q Developer not generating pull requests in repositories with branch protection rules
Problem: Amazon Q Developer isn't able to create a pull request in my GitHub repository, which has branch protection rules.
Solution: The branch protection rules prevents Amazon Q Developer from creating a branch to create a pull request. In order to use Amazon Q Developer for GitHub in repositories with branch protection rules, you need to add the Amazon Q Developer app to your allow list.
To add the Amazon Q Developer app to your allow list
-
If necessary, sign in to your GitHub
account using your GitHub credentials. -
Navigate to your GitHub organization, and then navigate to the repository you want to allow list the Amazon Q Developer for GitHub app.
-
Choose Settings, and then choose Branches from the navigation pane.
-
Under Branch protection rules, choose Edit to modify the branch protection rules.
-
Choose Restrict pushes that create matching branches, and search for the Amazon Q Developer for GitHub app.
-
Choose Save changes to allow Amazon Q Developer to create pull requests for issues with Amazon Q Developer labels.
To learn more about modifying branch protection rules in GitHub, see Creating a branch protection rule
Amazon Q Developer labels missing in GitHub issues
Problem: I don't see the Amazon Q development agent label in GitHub issues.
Solution: If the label isn't automatically created when you
installed the Amazon Q Developer for GitHub app, or it was unintentionally deleted, you can manually
create it in GitHub. The label must be named as Amazon Q development
agent in order for it to be
recognized and processed as a Amazon Q Developer label. For more information, see Creating a label
Amazon Q Developer not creating code for GitHub issues
Problem: I created a GitHub issue and invoked Amazon Q Developer to perform a task, but I got the following series of messages regarding technical difficulties:
-
⏳ I'm working on generating code for this issue. I'll update this issue with a comment and open a pull request when I'm done.
-
⚠️ I'm having technical difficulties. I couldn't solve the issue. I'm going to try again. This might take some time.
-
⚠️ I'm having technical difficulties. I couldn't solve the issue. I'm going to try again. This might take some time.
-
🔴 I'm having technical difficulties. I couldn't solve the issue.
Consider reassigning this issue to a user. This will help you stay within the quotas for generative AI feature usage.
Solution: If Amazon Q Developer is not able to process your issue and generate code for it, create a new issue and apply the Amazon Q development agent label to the new issue. To learn more about creating an issue and applying an Amazon Q Developer agent label, see Developing features and iterating with Amazon Q Developer in GitHub.
