NOTE: Our DC certified status has lapsed, but we are in the middle of re-applying. We expect Commit Graph to be DC certified within a few weeks!

-----

Fixed very serious bug related to build-status. Regression in previous fix caused build-status icon on "commits" and "all-branches-graph" to no longer be clickable ("undefined" in URL).

Two parts to fix:

• Changed logic to make sure that build-status is **never** touched on Bitbucket's native "commits" page (this was never supposed to be happening!).
• Also fixed the link to the build-status page from "all-branches-graph" so that clicking on build-status on "all-branches-graph" goes to the correct page.

Note: if you are running Commit Graph on a DC instance, the plugin manager will not see this release (we are currently recertifying for DC). You can force the plugin manager to take this upgrade by clicking on "Manage Apps" --> "Upload App" and then providing this URL: https://marketplace.atlassian.com/download/apps/1219256/version/202202075

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph's development.

( Revenue from PR-Booster also helps fund the development of our other free plugin: Control Freak Hook ).

( I would also mention Git Graph for Jira, except that thing is built like a tank and hasn't required any fixes in 2 years !)

---

Version v2021.09.15 of Commit Graph contains a single bugfix:

• Build-Status was no longer displaying on the "All-Branches-Graph" since Bitbucket 7.6.x. Fixed!

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph's development.

( Revenue from PR-Booster also helps fund the development of our other free plugin: Control Freak Hook ).

( I would also mention Git Graph for Jira, except that thing is built like a tank and hasn't required any fixes in 2 years !)

---

Version v2021.09.15 of Commit Graph contains a single bugfix:

• Build-Status was no longer displaying on the "All-Branches-Graph" since Bitbucket 7.6.x. Fixed!

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph's maintenance.

---

Version v2020.09.05 contains a single bugfix:

• Relative time for recent commits (e.g., "29 hours ago") was not displaying correctly on the All Branches Graph. Fixed!

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph's maintenance.

---

Version v2020.09.05 contains a single bugfix:

• Relative time for recent commits (e.g., "29 hours ago") was not displaying correctly on the All Branches Graph. Fixed!

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph's maintenance.

The work required to achieve Data Center certification in this release required a LOT of effort - we went through 3 review cycles with Atlassian engineers!

---

The main goal with this release was to finally achieve Data Center (DC) certification for Commit Graph.

Three small changes in this release:

• "master" was often included in all-branches-graph even if chosen filters specified that "master" should not be included. Fixed!
• Those same filters were using some internal Bitbucket API to figure out the branch prefix patterns. DC certification does not permit any usage of Bitbucket internal API, so we've refactored this logic to use public API instead.
• If a Branch-Model was not set for a given repository, a NPE error was getting thrown. Fixed!

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph's maintenance.

The work required to achieve Data Center certification in this release required a LOT of effort - we went through 3 review cycles with Atlassian engineers!

---

The main goal with this release was to finally achieve Data Center (DC) certification for Commit Graph.

Three small changes in this release:

• "master" was often included in all-branches-graph even if chosen filters specified that "master" should not be included. Fixed!
• Those same filters were using some internal Bitbucket API to figure out the branch prefix patterns. DC certification does not permit any usage of Bitbucket internal API, so we've refactored this logic to use public API instead.
• If a Branch-Model was not set for a given repository, a NPE error was getting thrown. Fixed!

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph's maintenance.

---

One small change in this release:

• Commit graph blows up with NullPointerException if the current repository does not have a branching-model. Fixed!
• (Note: previous version v2020.03.03 had a incomplete fix for this bug.)

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph.

---

One small change in this release:

• Commit graph blows up with NullPointerException if the current repository does not have a branching-model. Fixed!

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph.

---

The main goal with this release is to finally achieve Data Center (DC) certification for Commit Graph.

Two small changes in this release:

• "master" was often included in all-branches-graph even if chosen filters specified that "master" should not be included. Fixed!
• The filters were using some internal Bitbucket API to figure out the branch prefix patterns. DC certification does not permit any usage of Bitbucket internal API, so we've refactored this logic to use public API instead.

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph.

---

The main goal with this release is to finally achieve Data Center (DC) certification for Commit Graph. This version has been submitted for final review with Atlassian engineering staff and will hopefully soon become available for DC customers! (For now DC customers can manually install this "server" version - it should work fine and is byte-for-byte identical to the proposed DC version).

Two small changes in this release:

• "master" was often included in all-branches-graph even if chosen filters specified that "master" should not be included. Fixed!
• The filters were using some internal Bitbucket API to figure out the branch prefix patterns. DC certification does not permit any usage of Bitbucket internal API, so we've refactored this logic to use public API instead.

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph.

---

5 fixes:

• Improved memory utilisation. We removed all use of "session" temporary data caching. (This was previously used to speedup some git operations, especially "git merge-base" calls in previous versions of Commit Graph, but we have now refactored the data pipeline that feeds the graphs to make these caches unnecessary).
• Improved performance. Cut the number of git operations needed to render the "All Branches Graph" in half.
• Verified that all graph functionality behaves correctly on Safari, Chrome, Firefox, Edge, and IE11.
• Regression in v2019.10.01 if commit message contained "\u0004".
• In v2019.10.04 we improved error handling and commit parsing logic.

This version has been submitted for official Data Center certification. We expect to receive the certification within 4-8 weeks.

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph.

---

4 fixes:

• Improved memory utilisation. We removed all use of "session" temporary data caching. (This was previously used to speedup some git operations, especially "git merge-base" calls in previous versions of Commit Graph, but we have now refactored the data pipeline that feeds the graphs to make these caches unnecessary).
• Improved performance. Cut the number of git operations needed to render the "All Branches Graph" in half.
• Verified that all graph functionality behaves correctly on Safari, Chrome, Firefox, Edge, and IE11.
• Regression in v2019.10.01 caused graph to fail when commit message contained "\u0004" (ascii 4).

We believe this version to be very close to what will become our official Data Center certified version. We expect to receive the certification within 4-8 weeks.

Full changelog below the fold.

---

If you find Commit Graph useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Commit Graph.

---

3 fixes:

• Improved memory utilisation.We removed all use of "session" temporary data caching. (This was previously used to speedup some git operations, especially "git merge-base" calls in previous versions of Commit Graph, but we have now refactored the data pipeline that feeds the graphs to make these caches unnecessary).
• Improved performance.Cut the number of git operations needed to render the "All Branches Graph" in half.
• Verified that all graph functionality behaves correctly on Safari, Chrome, Firefox, Edge, and IE11.

We believe this version to be very close to what will become our official Data Center certified version of Commit Graph. We expect to receive the certification within 4-8 weeks.

Bug fixes:

• The search-for-commits feature on the All-Branches-Graph was vulnerable to XSS attacks (including the ability to craft and share malicious URLs).
• 1st attempt at fixing this (v2019.03.15) had an embarrassing^H^H^H^H^H^H^H^H^H^H critical regression that prevented the commit graph from rendering if the Bitbucket instance was connected to a Jira instance via an application link.

Compatibility Improvements:

• Bitbucket 6.1 compatibility: by default our integrated commit graph (on the commits screen) is disabled if you're using Bitbucket 6.1+ or newer, since Bitbucket 6.1.0+ now includes an integrated single-branch commit graph provided by Atlassian.

New Feature:

• The ability to enable/disable any Commit Graph feature can now be controlled at the repo or project level (e.g., if you want to disable all-branches-graph for a single repository or project, now you can).

This version now works on Bitbucket 6.x.

If you find our free Commit Graph app useful, please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server.

PR-Booster enhances your git workflow. Rebase, squash, amend, revert, and cherry-pick directly from Bitbucket. Ensure quality with automatic approvals retraction and needs-work retention. Save time with build status propagation. Revenue from PR-Booster helps fund maintenance for Commit Graph, as well as our other free apps.

New feature:

• Config screen with ability to enable/disable various parts of the graph.

Bugfixes:

• #49 - dependency issue - flagged by Atlassian
• #48 - search term not url-encoded
• #47 - tags missing on commits screen after 1st page
• #44 - search on IE11 broken

(Bitbucket 5.x version of 2018.07.05 release) The search box on the "All-Branches-Graph" is now able to find *branches* named after JIRA tickets. A search for "TKT-101" will now include branch "bugfix/TKT-101-fix-the-bug" in its results, even if that branch itself does not contain any *commits* with "TKT-101" in their commit messages.

Also threw in some minor cosmetic bugfixes with this release.

The search box on the "All-Branches-Graph" is now able to find *branches* named after JIRA tickets. A search for "TKT-101" will now include branch "bugfix/TKT-101-fix-the-bug" in its results, even if that branch itself does not contain any *commits* with "TKT-101" in their commit messages.

Also through in some minor cosmetic bugfixes with this release.

If a user typed in a JIRA ticket into the all-branches-graph, a server error 500 resulted.

Cause: typo in the "ao" reference: was "AoJiraIndex" instead of "AoJiraIndexResult".

Some bug fixes for when Bit-Booster - Rebase Squash Amend is co-installed. Both implement the same commit-graph functionality, and so we needed some logic to keep them from interfering with each other.

Bitbucket 4.x version:

Some bug fixes for when Bit-Booster - Rebase Squash Amend is co-installed. Both implement the same commit-graph functionality, and so we needed some logic to keep them from interfering with each other.