Uploaded image for project: 'Atlassian Product Integrations'
  1. Atlassian Product Integrations
  2. API-98

Bitbucket for Slack includes historical commits on new branch push

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      When a new branch is created in Bitbucket and the Slack channel has subscribed to the commits_pushed webhook a message will display in Slack which always contains the top 5 commits on the branch whether or not they are new to the repo. It would be ideal if only new commits were displayed when a new branch is pushed.  Raised from the community here: https://community.atlassian.com/t5/Bitbucket-questions/New-branch-notifications-in-Bitbucket-Cloud-for-Slack-have-too/qaq-p/1065630

       

      See also: https://confluence.atlassian.com/bitbucket/event-payloads-740262817.html#EventPayloads-Push

            [API-98] Bitbucket for Slack includes historical commits on new branch push

            LordSeb added a comment -

            I am waiting like one year so guys from Bitbucket fix this issue... I see its from 2019 .. its 2023!!!!! Must be a dream to work for Bitbucket when you can have issue open for 4 years and nobody gives a damn. Plese guys can we fix this already? Its pretty annoying, we are considering to switch fully to gitlab just because of this and the general approach of fixing things 4 years... guys please. 

            LordSeb added a comment - I am waiting like one year so guys from Bitbucket fix this issue... I see its from 2019 .. its 2023!!!!! Must be a dream to work for Bitbucket when you can have issue open for 4 years and nobody gives a damn. Plese guys can we fix this already? Its pretty annoying, we are considering to switch fully to gitlab just because of this and the general approach of fixing things 4 years... guys please. 

            Shane Mitchell added a comment -

            A fix for this would be great. The Bitbucket>Slack notification of first commit on a new branch is super confusing, and takes up a lot of vertical space in the subscribed channel.

            To summarize, when creating a new branch and committing for the first time, the commits_pushed Slack notification shows your new commits in that branch, PLUS all previous commits from the source branch. IMO: the historical source branch commits do not add anything of value, and shouldn't be displayed.

            Shane Mitchell added a comment - A fix for this would be great. The Bitbucket>Slack notification of first commit on a new branch is super confusing, and takes up a lot of vertical space in the subscribed channel. To summarize, when creating a new branch and committing for the first time, the commits_pushed Slack notification shows your new commits in that branch, PLUS all previous commits from the source branch. IMO: the historical source branch commits do not add anything of value, and shouldn't be displayed.

            marcins added a comment - - edited

            This should not be suggestion. This is a bug affecting many people and it's easy to confirm. Just create a repo, push several commits to it, then push new branch with 2 commits and on slack you'll get notification for pushing 5+ of them.

             

            Please focus on this issue as those notifications are really confusing.

            marcins added a comment - - edited This should not be suggestion. This is a bug affecting many people and it's easy to confirm. Just create a repo, push several commits to it, then push new branch with 2 commits and on slack you'll get notification for pushing 5+ of them.   Please focus on this issue as those notifications are really confusing.

              Unassigned Unassigned
              swaters Sean Waters
              Votes:
              10 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: