GitHub for Atlassian vs GitHub for Compass

[Paul O_Shaughnessy]

The GitHub for Atlassian app on the marketplace appears to work with Compass 

Use GitHub development and security data across your Atlassian apps, like Jira, Compass, Rovo, and more. Get end-to-end visibility of your work and SDLC, with the right context in the right place and at the right time.

But on the Compass marketplace there is a different app: GitHub for Compass.

What is the difference between these apps? 

I need to hook up to a GHES and this seems to be possible with GitHub for Atlassian but only possible with Webhooks on the GitHub for Compass app.

Can I just use GitHub for Atlassian and configure my GHES connectivity to see events in Compass? I'd much rather use this method than the webhook approach on offer in GitHub for Compass

[Enrique Serrano Valle]

Hi, @Paul O_Shaughnessy !

We're currently soft-rolling a seamless integration between GitHub for Atlassian and Compass, which is the preferred and default integration for Compass today for new Compass sites, as long as Jira and GitHub for Atlassian are already installed and configured, with US as their data residency region.

I believe the integration of Compass and GitHub for Atlassian can work for GHES - you're right that the Compass (Forge) GitHub App doesn't support this kind of integration, and that the other alternative would be using a GitHub Server incoming webhook.

If your site would meet the requirements for the GitHub for Atlassian integration, all you need to do is to provision a new Compass site and complete the onboarding flow - if your Jira projects are already connected with your GitHub instance, you'll see some of them imported from the beginning and starting to receive events and subsequently metric and health scorecard value updates.

You can also keep adding new connected Compass Components to your site using the Create > Import Components > Jira > Import option of your Compass instance.