aws-amplify / aws-amplify/amplify-hosting

Allow multiple GitHub sources/authorizations

Open
#735 5 comments 4 reactions 0 assignees View on GitHub
feature-request
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
Currently, amplify console will ask for github authorization the first time. The next time, it will by default continue with the same github credentials. It is not possible to deploy from more than one github account credentials. It is also not possible to deploy repo from one account and repo from the organization(s) that account is associated with.

**Describe the solution you'd like**
It should be possible to choose from existing github authorizations or create a new one for every manual deploy/connect app action from Amplify Console.

**Additional context**
This could also apply for Bitbucket/Gitlab if a similar approach to Github is followed.

Contributor guide

Open the contributing guide

Research direction

The issue does not identify specific files, tests, or entry points. Start by tracing the Amplify Console manual deploy and connect-app authorization flows, then determine how existing GitHub authorizations are stored and selected. Done means users can choose an existing authorization or create a new one for each action without breaking current deployments.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, github
Domain
authentication, ci-cd, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.