Our integration of Confluence and GitHub enhances documentation and establishes a connection between the two platforms. Now with Engineering Reporting: see your team's delivery metrics - PR cycle time, throughput, and review latency - live on the page.
GitHub private and public repositories can be integrated with Confluence to enhance the usefulness of your documentation.
Include details about your release, milestones, and tags to enhance the quality of your release documentation.
Streamline your software development lifecycle by displaying GitHub pull requests, issues, labels, and assignees with updated statuses and other useful data.
Watch 2-minute demo of GitHub links for Confluence
Paste a GitHub URL into Confluence and it renders live - source code files, READMEs, and repository content update automatically. Syntax highlighting is preserved, and it works with private repos. Now with Engineering Reporting, the same app shows team-level delivery metrics - PR cycle time, throughput, and review latency - live on the page, computed from the GitHub API at view time. We store no code or PR data, and reporting reuses your existing GitHub connection.
Engineering teams writing technical documentation, developer experience (DevEx) teams maintaining internal portals, and technical writers embedding code in Confluence. Any team where Confluence pages reference GitHub code - API docs, architecture docs, onboarding guides, design reviews.
The moment you copy code from GitHub into a Confluence page, it's stale. When the code changes (and it will), nobody updates the Confluence page. Technical docs become unreliable, and teams stop trusting them.
Paste a GitHub URL into Confluence and it renders live - source code files, READMEs, and repository content update automatically. Syntax highlighting is preserved, and it works with private repos. Now with Engineering Reporting, the same app shows team-level delivery metrics - PR cycle time, throughput, and review latency - live on the page, computed from the GitHub API at view time. We store no code or PR data, and reporting reuses your existing GitHub connection.
A platform team maintains API documentation in Confluence for internal consumers. The documentation references specific GitHub repositories, code files, and README content. When developers read the docs, they need to see the current state of the code, not a stale copy.
The challenge: The platform team pastes code snippets from GitHub into Confluence pages. These snippets become outdated the moment the code changes. Developers follow outdated examples from the documentation and submit pull requests that do not compile. The platform team spends time answering questions that would be resolved if the documentation reflected the current code.
How GitHub Links for Confluence helps:
The result: Documentation stays current automatically. Developers trust the Confluence pages because the code examples always match the actual repository. Support requests to the platform team decrease because the documentation is accurate.
An engineering team documents architecture decisions in Confluence ADR pages. Each ADR references the pull requests that implement the decision. Readers need to see the PR status to understand whether the decision has been fully implemented.
The challenge: ADR pages include plain URLs to GitHub PRs. Over time, readers cannot tell which PRs were merged, which were abandoned, and which are still open. The ADR reads as if the decision was implemented, but some PRs may have been closed without merging.
How GitHub Links for Confluence helps:
The result: ADR pages are living documents that show the real implementation status. New team members reading historical ADRs can distinguish between fully implemented decisions and partially completed ones.
A company maintains several open source libraries on GitHub. The internal Confluence wiki serves as the coordination hub where the team plans releases, tracks contributions, and documents internal processes. External contributors use the GitHub README and wiki.
The challenge: The internal team needs to see GitHub activity without constantly switching to GitHub. They want to track issue counts, PR backlog, and release status from Confluence. Manually updating these numbers in Confluence is tedious and always outdated.
How GitHub Links for Confluence helps:
The result: The internal team manages open source projects from Confluence with real-time GitHub context. Planning meetings reference live data instead of stale screenshots. The team catches backlog growth early because issue counts are always visible.
An engineering manager runs sprint reviews and quarterly business reviews from Confluence. They want a quick, honest read on delivery health - without exporting data or standing up a separate analytics platform.
The challenge: Delivery metrics usually live in a tool nobody opens during the meeting, so reviews rely on stale screenshots or gut feel.
How GitHub Links for Confluence helps:
The result: QBR and team-health pages show current, team-level delivery signals where the conversation already happens - included in the app, with no separate platform.
We prioritize customer data privacy with GDPR-compliant data collection and processing.
Atlassian Marketplace Partners don’t have the tools to manage licenses, so you need to reach out to Atlassian Support.
You can renew the trial to extend your evaluation period up to 5 times. Afterwards, you will need to contact Atlassian and seek an approval from Atlassian Marketplace Partner.
For more details check out this blog.
