This version includes a new merge check to ensure that all submodules can be merged to the default branch in fast-forward mode. If we didn't merge the submodule before merging the main repository, we'd be able to do it afterward in fast-forward mode, and the link to the submodule will remain unchanged. 

Please note that merge check only works for submodules hosted in Bitbucket it's been enabled in. The validation is performed only at the first level of a submodule, and nested submodules will not be checked. Also, if the list of changes is truncated for it is too large to render and the modified submodule didn't appear in the rendered list, it will not be analyzed in this merge-check.

Merge-check must first be enabled in the project or repository settings.

This version includes a new merge check to ensure that all submodules can be merged to the default branch in fast-forward mode. If we didn't merge the submodule before merging the main repository, we'd be able to do it afterward in fast-forward mode, and the link to the submodule will remain unchanged. 

Please note that merge check only works for submodules hosted in Bitbucket it's been enabled in. The validation is performed only at the first level of a submodule, and nested submodules will not be checked. Also, if the list of changes is truncated for it is too large to render and the modified submodule didn't appear in the rendered list, it will not be analyzed in this merge-check.

Merge-check must first be enabled in the project or repository settings.

Disabled showing submodule changes when a submodule is just added in shown changes

Disabled showing submodule changes when a submodule is just added in shown changes

Fixed the issue with the app failing to display submodule hash changes in the following cases:

• Submodule contains conflict changes,
• Bitbucket can not receive submodule content changes.

Fixed the issue with the app failing to display submodule hash changes in the following cases:

• Submodule contains conflict changes,
• Bitbucket can not receive submodule content changes.

Fixed issue with the app failing to display changes in pull requests made from a forked repository.

Fixed issue with the app failing to display changes in pull requests made from a forked repository.

Fixed issue with the view entire source for this file button not working for a file in submodule.

Fixed issue with the view entire source for this file button not working for a file in submodule.

Fixed in this release:

• The issue with the app failing to commit changes when edited online with Bitbucket.

Fixed in this release

• The issue with the app failing to commit changes when edited online with Bitbucket.

🎉 Support of recursive Git submodules

We've supported recursive Git submodules which makes it possible to watch the diff for pull requests and commits where multiple levels of submodule repositories were changed. Before that, the app only supported viewing the repositories one level down.

The new feature is a solution for reviewing enterprise multi-repo projects where you had to switch between hundreds of pull requests for minor changes and it's hard to get a grasp of what's actually being changed.

👀 Important note about the licensing

From version 2.0, Submodule Changes for Bitbucket will become a paid app. Once you update, your 30-day trial period will start.

✅ Compatibility with Bitbucket

The app becomes compatible with Bitbucket Server and Data Center versions 6.0 and above.

🚀 Roadmap

Read the details about the future roadmap for the app here to get an overview of what we're going to add to the app.

🎉 Support of recursive Git submodules

We've supported recursive Git submodules which makes it possible to watch the diff for pull requests and commits where multiple levels of submodule repositories were changed. Before that, the app only supported viewing the repositories one level down.

The new feature is a solution for reviewing enterprise multi-repo projects where you had to switch between hundreds of pull requests for minor changes and it's hard to get a grasp of what's actually being changed.

👀 Important note about the licensing

From version 2.0, Submodule Changes for Bitbucket will become a paid app. Once you update, your 30-day trial period will start.

✅ Compatibility with Bitbucket

The app becomes compatible with Bitbucket Server and Data Center versions 6.0 and above.

🚀 Roadmap

Read the details about the future roadmap for the app here to get an overview of what we're going to add to the app.

New in this release:

The app is now Data Center approved.

New in this release:

The app is now Data Center approved.

In this release, we've fixed the issue that happened while viewing the commits with changes to the submodule in a super-repo if a user didn't have access to the submodule.

In this release, we've fixed an issue that occurred if the submodule or its super repository was moved to another directory within the same Bitbucket instance. Errors occurred in case the .gitmodules file specified a URL to a different repo than the git link recorded in the super repository.

In this release, we've added a possibility to turn off the app for certain submodules.

In some cases, the number of changes in a pull request with a submodule can exceed the page.max.changes limit. For instance, when a dependency on some large project is used as a submodule. That resulted in an incomplete displaying of changes in the pull request diff view.

To disable the Submodule Changes for Bitbucket app for a specific submodule in a repository, you need to add a special property in the .gitmodules file using the following Git command:

• git config --file .gitmodules submodule.<name>.ignoreChanges true

In this command, <name> is the submodule name specified in the [submodule "<name>"] section of the .gitmodules file. The changes will be applied after you commit and push them. Read more about it here.

In this release, we've fixed the issue that happened while comparing branches with a new submodule in the destination branch. The issue occurred on the Compare branches page.

In this release, we've fixed the issue caused by using the submodule URL relative to the super-repository.

Fixed a bug with the Source tab displaying. The issue occurred while viewing the contents in the files with the same name as the submodule.

In this release:

We have added compatibility with Bitbucket Server 6.6.

The app from StiltSoft, the creator of Awesome Graphs for Bitbucket, that provides the statistics for projects and repositories and helps to analyze and evaluate development team performance, code review practices and personal activity of each team member.

If you use Git submodules workflow, you may probably face the problem when changes to the submodule in the Diff tab are shown as two commit hashes, not the code that's actually changed. It is difficult to find modified files and almost impossible to review pull requests, leave comments and suggest improvements to them.

Submodule Changes for Bitbucket app helps:

• Show the changes committed to a submodule in the Diff tab as if they're committed to the parental repository. Instead of two commit hashes, you'll see highlighted added, deleted or modified lines of code.
• Comment on the entire pull request, a particular file, or on specific lines of code in a file that were changed in a Git submodule.