aws-amplify / aws-amplify/amplify-hosting
Authorize GitHub App permission error
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [ ] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [ ] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [ ] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [ ] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
### App Id
d1sj4cr45c2t8p
### Region
us-east-1
### Amplify Hosting feature
_No response_
### Describe the bug
Got an error when i try to Migrate to Amplify GitHub App.
Error message : "We do not have permission to access this repository. Please update your permissions and try again."
Github permissions looks correctly set for the repo.
I tried to delete the deploy keys and webhooks but it's not working. And now i can't deploy anymore with the previous OAuth access. So I'm stuck.
### Expected behavior
When i click on reconnect the repo, i can migrate to Amplify Github App. The permissions are enough to create deploy keys and webhooks and i can re-connect my repo and deploy my app.
### Reproduction steps
1. Click on the "Start migration" button.
2. Error shown
3. Click on the "update repository permissions"
4. All permissions are set for the repo. Can't go further.
### Build Settings
_No response_
### Additional information
_No response_
Contributor guide
Research direction
No source files or tests are named in the report. Start by reproducing the migration in the stated us-east-1 region with the provided reproduction steps, then inspect the GitHub App permission and repository reconnection flow. Done means a repository with the stated permissions can migrate, reconnect, and deploy without the reported access error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100