Compass: GitHub Integration not successful
Asked by Ronny Katzenberger:

We run GitHub Enterprise Cloud and are trying to get Compass integrated.  
I had an GitHub Enterprise owner set up as admin in Compass and had him install the GitHub App in Compass.

We walked through the steps and selected a specific repository instead of all repos, so that we can limit our evaluation in scope.

Once done, Compass does not provide any sort of indication of the integration was successful. If I check on the GitHub App page in Compass, I get a screen which doesn't seem to indicate that this was a success:

![2024-03-01_15-41-59.png](https://community.atlassian.com/t5/image/serverpage/image-id/309784i4E305169C62A25DB/image-size/large?v=v2&px=999 "2024-03-01_15-41-59.png")


Answers:
author: Enrique Serrano Valle
body: [@Ronny Katzenberger](/t5/user/viewprofilepage/user-id/5252046) let's see if we can get this solved. The fact that you aren't seeing any connected workspace in the screenshot of the "Compass GitHub App" screen that you provided suggests that something didn't work as expected during the Compass - GitHub connection.

There's a specific situation where attempting to connect a GitHub organization when such organization already has a "GitHub Compass App" installed (that is, the "Compass" application already installed in "GitHub") that results in no successful installation and not a lot of visual feedback either.

For example, if in the screenshot below I selected any of the two organizations where the "GitHub Compass App" were already installed (that display the "Configure \>" option), I would not be redirected back to the "Compass GitHub App" and Compass would not be connected successfully to GitHub. (If a Compass Admin and GitHub admin selected an organization that didn't have any "GitHub Compass App" installed - like the third row in the screenshot - the process should complete successfully.)

![Screenshot 2024-03-05 at 2.18.22?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/310371iD55ACAE6F4A69E68/image-size/large?v=v2&px=999 "Screenshot 2024-03-05 at 2.18.22?PM.png")

Is this something similar to the scenario that you encountered? If so, the following steps may help solve it:

1. Uninstall the "GitHub Compass App" from GitHub. You'd find it in the <https://github.com/organizations/your-organization-here/settings/installations> section, and you can remove it in the "Configure" button related to the "Atlassian Compass" GitHub app.
2. Have a Compass Admin (also being a GitHub Admin) configure the GitHub connection inside of Compass. When selecting the organization to connect, you would see just an arrow \`\>\` instead of the \`Configure \>\` option.
3. Completing this should redirect you back to Compass once you select repositories and accept. (If there's no redirection back to Compass, something would still be missing.)

Please let me know whether the steps above helped, or whether we need to try something else.

comments: author: Ronny Katzenberger
body: Will check on that.

Would there be a chance that this Compass integration would conflict with an existing JIRA to GitHub integration?


author: Enrique Serrano Valle
body: Thanks, Ronny. Let me know how that goes.

Theoretically it shouldn't conflict with the official GitHub for Jira app, but I also gave it a test in a couple of my sites, and I was able to complete the installation without an issue so far.


author: Ronny Katzenberger
body: Thanks for the tip [@Enrique Serrano Valle](/t5/user/viewprofilepage/user-id/5100732) - it looks like this was the issue and our team was able to get it working yesterday.


author: Andy Olson
body: We are running into an issue very similar to this, but the resolution steps above didn't resolve it. Rough steps:

1) Install Github app from Compass.

2) Click connect.

3) Click Configure for our organization at the Github prompt.

4) Taken directly to a github permissions page which correctly says our SRC repo has Read permissions with Compass. No obvious workflow at this point, just the information page.

5) Back in Compass, import from the "Create" option takes us to the same place.

comments: author: Enrique Serrano Valle
body: Hi, [@Andy Olson](/t5/user/viewprofilepage/user-id/5482705) !

Based on your description and the mention on Step 3 to "Configure", I'm guessing that when you started the connection flow from Compass itself, the "Compass App" in GitHub was already installed for that organization.

If selecting the target organization doesn't redirect you back to Compass, the connection won't complete successfully. (You'd need to see a row without the "Configure" prompt; see my screenshot above <https://community.atlassian.com/t5/Compass-questions/Re-Compass-GitHub-Integration-not-successful/qaq-p/2630557/comment-id/530#M530>)

Uninstalling the "Compass App" in GitHub for the given organization typically resolves that, since the "Configure \>" option goes away in further Compass-initiated connection attempts, and the redirect back to Compass completes the installation successfully. Let me know if that works!


author: Enrique Serrano Valle
body: [@Andy Olson](/t5/user/viewprofilepage/user-id/5482705) our team has recently rolled a fix in the latest version of the GitHub app for a rare edge case where an organization is connected after a different user had connected another organization. I remembered your case and I wondered whether that was what you were experiencing. Please don't hesitate to give it a try and let me know whether that addressed your issue.


author: Will Freeman
body: I am running into the same situation here; I have uninstalled the Compass app from GitHub and the GitHub app from Compass and tried again, but it quickly reverts to the same problem and doesn't list any of the repositories.


author: Enrique Serrano Valle
body: [@Will Freeman](/t5/user/viewprofilepage/user-id/5512121) if you have already upgraded your GitHub app inside of Compass to the latest version, can you log a support ticket with Atlassian, with the details of your site and what you encounter through your installation flow? That could help troubleshoot some specific problem.