Fix forge credential connection approval flow
When adding a GitHub or any other forge credential, now user sees instant blink of the page and his current (whatever is current) github login is connected, this is incorrect. Should be: user is presented with the screen where he approves the connection (and/or app installation) and can switch to another account and/or choose repositories he wants Jaah to be connected to.
Outcome
GitHub + Azure DevOps Connect now show the account picker (prompt=select_account); GitHub carries zero-reach connects to the App install page to pick repos. GitLab/Bitbucket unchanged per operator. Full gate green; PR #4605 merged.
Artifacts
Activity
- Created
- Run
- Runner started
- Awaiting response
- Awaiting response
- Awaiting response
- Awaiting response
- Runner resumed
- Awaiting response
- Awaiting response
- Runner resumed
- Awaiting response
- Awaiting response
- Runner resumed
- Runner ended (done)