Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-2896

Diff between original commit and amended/rebased commit

    • 188
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      In stash 1.3, if you push a branch, and then (usually in response to the discussion) amend or rebase the branch, then push -f to updated, the pull request discussion shows added + removed commits.

      However, there is no obvious way to compare the original state of the branch with then new branch to see what changed.

            [BSERV-2896] Diff between original commit and amended/rebased commit

            e43651f12c0f: On the pull request "Overview" tab in the "Activities" section, on every activity that updates the scope of the pull request, such as a push or a rebase, it says "<Name> UPDATED the pull request by adding/removing X commits (view changes)". The "view changes" link is there.

            Wolfgang Kritzinger added a comment - e43651f12c0f : On the pull request "Overview" tab in the "Activities" section, on every activity that updates the scope of the pull request, such as a push or a rebase, it says "<Name> UPDATED the pull request by adding/removing X commits (view changes) ". The "view changes" link is there.

            wkritzinger 

            Where is  "view changes" link?

            We are using 7.18.0 and I can't find it.

            Michelle Geppert added a comment - wkritzinger   Where is  "view changes" link? We are using 7.18.0 and I can't find it.

            Hi all,

            As mentioned above, this has been fixed by a change in Bitbucket Server and Data Center version 7.11.1.

            There is now a "view changes" link on push activities in a pull request, which takes you to the diff view and shows the effective changes that were applied to the pull request during that push activity. This includes force pushes and other scope changes, such as when changing the target branch of the pull request.

            Thanks,
            Wolfgang Kritzinger
            Bitbucket Senior Developer

            Wolfgang Kritzinger added a comment - Hi all, As mentioned above, this has been fixed by a change in Bitbucket Server and Data Center version 7.11.1. There is now a "view changes" link on push activities in a pull request, which takes you to the diff view and shows the effective changes that were applied to the pull request during that push activity. This includes force pushes and other scope changes, such as when changing the target branch of the pull request. Thanks, Wolfgang Kritzinger Bitbucket Senior Developer

            This now exists in Bitbucket Data Center and Server version 7.17.2.
            There is a new "view changes" option.

            Aidan Gallagher added a comment - This now exists in Bitbucket Data Center and Server version 7.17.2. There is a new "view changes" option.

            Srinivas Narayan added a comment - - edited

            +1. 

            It is really frustrating to see a basic feature like this not being available after the problem was reported 8+ years ago.

            Srinivas Narayan added a comment - - edited +1.  It is really frustrating to see a basic feature like this not being available after the problem was reported 8+ years ago.

            +1!

            ella added a comment -

            +1

            ella added a comment - +1

            Came here just to see if anyone at Bitbucket is working on this. Sad to find an 8 year old stale ticket...

            Gitlab and Github have had this for years! Please 🙏

            I fully agree with @Antoine Morisseau.

            Sebastian Mandrean added a comment - Came here just to see if anyone at Bitbucket is working on this. Sad to find an 8 year old stale ticket... Gitlab and Github have had this for years! Please  🙏 I fully agree with @Antoine Morisseau.

            ValkaHonda added a comment -

            This feature will be really useful!

            ValkaHonda added a comment - This feature will be really useful!

            I just sent a feedback on Bitbucket for this very feature.

            I cannot believe it's not in the new pull request experience feature list : https://support.atlassian.com/bitbucket-cloud/docs/try-the-new-pull-request-experience-in-bitbucket/

            Gitlab does it for years and it's very useful to keep a clean commit history.

            Maybe create a BCLOUD ticket for this feature ? could @jarredc see this and take care of it ?

            Antoine Morisseau added a comment - I just sent a feedback on Bitbucket for this very feature. I cannot believe it's not in the new pull request experience feature list : https://support.atlassian.com/bitbucket-cloud/docs/try-the-new-pull-request-experience-in-bitbucket/ Gitlab does it for years and it's very useful to keep a clean commit history. Maybe create a BCLOUD ticket for this feature ? could @jarredc see this and take care of it ?

              Unassigned Unassigned
              7922e4d89576 Yair Zadik
              Votes:
              156 Vote for this issue
              Watchers:
              101 Start watching this issue

                Created:
                Updated:
                Resolved: