Each plan and branch should have the option to track revision and Build status by git tree hash not commit hash. This way if a commit is merged to several branches, and the commit message is not used by the build, only one build is done for the tree.

If the commit does not relate to the files that are built, but if no files change the binaries will be identical, the build should be tracked by the tree and not the commit hash. The commit hash and commit message can change with a force push. But the tree hash will only change when any files changes. This option tracks to the build artifacts much closer then the commit hash in this case.

Here is a standard commit message:

$ git cat-file -p 2cfe7c3fcf3c1bdddf595c01ddc4a8c6ba7864e9
tree e22ca8d045d076bbf307dc1a15bbd12bb162956e
parent c56aee5bfee6135735cf47326f0c237fdfc19352
parent 2ccc6a9ebb5ad22de6a6b77d86e0b6441d1b8607
author dave laser <dlaser@atlassian.com> 1639781568 +0000
committer dave laser <dlaser@atlassian.com> 1639781568 +0000

Pull request #4: ...

Option to track revision e22ca8d0, tree, not 2cfe7c3f, commit hash.

Expected Results

An option to report build revision by tree and not commit hash. If two commits have the same tree, the build status is reported without the build being run and all links go back to the original build showing both commits.

Actual Results

Each commit can get a build. Separate commits with the same tree, and possibly the same binaries, will have separate builds and different revisions. The status reported back will be linked by commit message not tree.