GitHub links for Confluence: Cloud and Data Center Comparison
This page summarises the differences between GitHub links for Confluence (Data Center) and GitHub links for Confluence (Cloud).
Connection
Capability | Data Center | Cloud |
|---|---|---|
Connect via GitHub Personal Access Token | ✅ | ✅ |
Connect via GitHub App | ❌ | ✅ |
Global (admin-level) connection | ✅ | ✅ |
Per-user (personal) connection | ❌ | ❌ |
Multiple integrations support | ❌ | ❌ |
Supported macros
GitHub links for Confluence uses a single GitHub Links macro that renders different GitHub entities based on the URL provided. The table below shows which entity types each version of the macro can render.
Macro/supported URL type | DC | Cloud |
|---|---|---|
GitHub Issue | ✅ | ✅ |
GitHub Issues list | ✅ | ✅ |
GitHub Pull Request | ✅ | ✅ |
GitHub Pull Requests list | ✅ | ✅ |
GitHub Repository | ❌ | ✅ |
GitHub Branch | ❌ | ✅ |
GitHub Source File | ❌ | ✅ |
GitHub Source File line range | ❌ | ✅ |
GitHub Account | ❌ | ✅ |
GitHub Release | ❌ | ✅ |
GitHub Milestone | ❌ | ✅ |
Global configuration settings
Setting | Data Center | Cloud |
|---|---|---|
Date format (date format used when rendering dates inside macros) | ✅ | ❌ |
Repository access scope (limit which repositories the integration can read) | ❌ Governed by PAT scope only | ✅ Configured per organisation via the GitHub App |
Hosting & deployment
Capability | Data Center | Cloud |
|---|---|---|
Works with GitHub.com (SaaS GitHub) | ✅ Yes | ✅ Yes |
Works with self-hosted GitHub Enterprise Server (GHES) | ❌ | ❌ |
Need help?
If you have questions about the differences above, please contact the Move Work Forward Support team. We'll be glad to help.
Updated: