# Forge "Runs on Atlassian" and GitHub Connection

**URL:** <https://community.developer.atlassian.com/t/forge-runs-on-atlassian-and-github-connection/102130>\
**Category:** Forge\
**Tags:** github, oauth2, gitlab, runs-on-atlassian, forge\
**Created:** [August 12, 2026, 10:11am UTC](https://community.developer.atlassian.com/t/forge-runs-on-atlassian-and-github-connection/102130 "2026-08-12T10:11:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![PaulLunkenheimer](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/paullunkenheimer/32/54839_2.png) [@PaulLunkenheimer](https://community.developer.atlassian.com/u/PaulLunkenheimer)\
**Post date:** [August 12, 2026, 10:11am UTC](https://community.developer.atlassian.com/t/forge-runs-on-atlassian-and-github-connection/102130/1 "2026-08-12T10:11:24Z")

</div>

Hello,

We are currently in the process of migrating an Atlassian Connect Express app to Forge.

This app offers users the possibility to connect to GitHub / GitLab and pull and push certain files.

Can we migrate this functionality to Forge and also become a “Runs on Atlassian” app?

I found [this](https://developer.atlassian.com/platform/forge/use-an-external-oauth-2.0-api-with-fetch/) tutorial, but it seems to use remotes, which [contradictes](https://developer.atlassian.com/platform/forge/runs-on-atlassian-apps/) the "Runs on Atlassian rules.

---

<div class="post-metadata">

**Author:** ![HeyJoe](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/heyjoe/32/39049_2.png) [@HeyJoe](https://community.developer.atlassian.com/u/HeyJoe)\
**Post date:** [August 12, 2026, 11:43am UTC](https://community.developer.atlassian.com/t/forge-runs-on-atlassian-and-github-connection/102130/2 "2026-08-12T11:43:03Z")

</div>

Hi @PaulLunkenheimer ,

No, it’s not possible to build an app that initiates connections to Github/GitLab and have it quality for Runs on Atlassian (“RoA”)

The Runs on Atlassian [eligibility rules](https://developer.atlassian.com/platform/forge/runs-on-atlassian-apps/#eligibility-of-apps) have a comprehensive list of what disqualifies an app.

You can, however, use the [Customer-managed Egress & Remotes](https://developer.atlassian.com/platform/forge/customer-managed-egress-and-remotes/) feature to build an app that is completely Forge hosted _except_ for egress rules that are dynamically configured and approved at runtime by the customer. While this isn’t _quite_ RoA, it does present a data security posture that customer subsets will find strongly preferable. For example this style of integration is strongly preferred for [Isolated Cloud apps](https://developer.atlassian.com/platform/marketplace/publish-and-list-ic-apps/) compared to a fully remote app.

The decision to exclude customer-managed egress & remotes from Runs on Atlassian was/is a contentious one. You can find other discussions here in the developer community about it.

To summarise; you can’t get to “Runs on Atlassian”, but you can get to “as fully Forge hosted as possible, with data only shared with existing third-party SaaS vendors”, which has customer value but isn’t as well surfaced on the Marketplace with a special badge.

---

<div class="post-metadata">

**Author:** ![PaulLunkenheimer](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/paullunkenheimer/32/54839_2.png) [@PaulLunkenheimer](https://community.developer.atlassian.com/u/PaulLunkenheimer)\
**Post date:** [August 13, 2026, 6:27am UTC](https://community.developer.atlassian.com/t/forge-runs-on-atlassian-and-github-connection/102130/3 "2026-08-13T06:27:23Z")

</div>

Hey @HeyJoe,

Thank you so much for this extensive answer. That fully covers my question and helps us a lot to build the right product for our existing customers and potential new users.

Best,

Paul