Summary
When a user installs the Sola GitHub App on a specific repository and later tries to create another integration for a different repository, they may get stuck on GitHub’s authorization screen and never be redirected back to Sola.
Issue Description
A user initially installed the Sola GitHub App on a single repository and successfully created an integration in Sola.
Later, the user attempted to add another GitHub integration for a different repository.
When initiating the integration flow from Sola:
Sola redirected the user to GitHub for authorization.
On GitHub, the user completed the app authorization / repo selection.
However, the flow got stuck on GitHub’s side - there was no redirect back to Sola.
As a result, the new integration could not be completed.
Workaround / Resolution
Option 1:Clean, Simple, Not immediate
Instead of creating a 2nd integration - Just go to Githubb, Edit the Sola app to include the relevant repositories and click Save.
The repositories will be updated in the next sync cycle.
Option 2:Remove the Integration from both Sola & Github, and create a new integration with all the required repo.
Go back to sola
High level:
Remove the existing GitHub integration and app, then reinstall and configure again.
Steps:
In Sola
Go to Integrations.
Locate the existing GitHub integration for the user.
Delete / disconnect the existing GitHub integration.
In GitHub
Go to Settings (user or organization level - wherever the app was installed).
Open Installed GitHub Apps.
Find the Sola app.
Remove / uninstall the Sola app.
Reinstall the GitHub App
Go back to Sola → Integrations → GitHub.
Start the integration flow again.
When redirected to GitHub, install the Sola GitHub App and select the desired repositories (including any additional repos the user wants to integrate).
Re-create Integrations in Sola
After successful redirect back to Sola, create the new GitHub integration(s) for the required repositories.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article