In Crucible you could drag a range between two commits in a code review. This was very useful, if you returned to the review after a while and was interested only in a set of commit changes. Particularly useful if a bunch of commits actually did some back and forth changes and you are not interested in the mid-steps only in the end result.
On bitbucket I can check changes of the whole PR, or individual commit changes. Is there a way to see changes for a range of commits, or I'm unlucky? Is this planned? Or is it for some reason difficult, unfeasible for Atlassian to do?
Hey @simon democko , we have added the missing compare view in Bitbucket 6.3:
Thanks,
Maciej
Hi! I meant within the pull request itself, this requires to go and copy the commit numbers from the PR into this interface, which is cumbersome. But definitely an improvement.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the answer. We don't have any UI for doing that but you could try using the small hidden feature of Pull Request.
If you know the commit hashes you could prepare the custom URL for the pull request:
https://your-stash-instsance.com/projects/PROJECT-NAME/repos/repo-name/pull-requests/123456/commits/<<git-commit-id-A>>?since=<<git-commit-id-B->>
This will show you the custom diff. As you said that's a cumbersome solution. If you feel like we should add the feature into Bitbucket please raise a feature request ticket on https://jira.atlassian.com/browse/BSERV
Thanks,
Maciej
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For anyone interested, you can vote on this feature suggestion here: https://jira.atlassian.com/browse/BSERV-12260
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For anyone interested, you can vote on this feature suggestion here: https://jira.atlassian.com/browse/BSERV-12260
_______________
Mad's good workaround answer for better visibility:
We don't have any UI for doing that but you could try using the small hidden feature of Pull Request.
If you know the commit hashes you could prepare the custom URL for the pull request:
https://your-stash-instsance.com/projects/PROJECT-NAME/repos/repo-name/pull-requests/123456/commits/<<git-commit-id-A>>?since=<<git-commit-id-B->>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.