Bitbucket Server 5.0 will introduce Commit.getCommitter(), Commit.getCommitterTimestamp(), Blame.getCommitter() and Blame.getCommitterTimestamp(). The new properties are available via both the Java API and the REST API.
In addition, Bitbucket Server 5.0 also introduces the ability to pass an explicit committer to MergeCommandParameters when creating merges, allowing plugin developers to control author and committer independently. If one is provided and not the other, it will be used for both (so if you only provide an author, they'll also be the committer, and if you only provide a committer, they'll also be the author).
Rendering the new data in the UI will be tracked separately on BSERV-8868. Changes to how pull request merges are handled are also tracked separately, on BSERV-4415. This issue only tracks the API enhancement.
Best regards,
Bitbucket Server 5.0 will introduce Commit.getCommitter(), Commit.getCommitterTimestamp(), Blame.getCommitter() and Blame.getCommitterTimestamp(). The new properties are available via both the Java API and the REST API.
In addition, Bitbucket Server 5.0 also introduces the ability to pass an explicit committer to MergeCommandParameters when creating merges, allowing plugin developers to control author and committer independently. If one is provided and not the other, it will be used for both (so if you only provide an author, they'll also be the committer, and if you only provide a committer, they'll also be the author).
Rendering the new data in the UI will be tracked separately on
BSERV-8868. Changes to how pull request merges are handled are also tracked separately, onBSERV-4415. This issue only tracks the API enhancement.Best regards,