v1.20.2Website
•1 min read

Choosing Which GitHub Account to Connect

Connecting GitHub now asks which GitHub account to authorize, and which of its installations this project syncs to, instead of silently taking whichever account the browser happened to be signed in as.

#What's Changed

  • [Fix] GitHub authorized whichever account the browser was signed in as, without asking, so anyone signed in to more than one GitHub account could not connect the other one. GitHub's account picker is now always shown, and the account you choose is the one that connects.
  • [Feature] When the GitHub user you authorize with can reach ApiVault's app on several accounts or organizations, ApiVault asks which one this project should sync to, instead of picking for you. The list holds your own account and the organizations you authorized with, never someone else's personal account that GitHub lists because you collaborate on its repositories. Accounts the project already runs on are left off too, so Connect Another GitHub Account offers only what is actually another account.
  • [Improvement] The account chooser can send you to GitHub to install the app on an account that does not have it yet, so a newly created organization is one click away instead of a dead end. Only accounts that already have the app can be connected, and the chooser now says so.