Compare view v2.0 – diff between forks

By on March 4, 2011

Three weeks ago we introduced the “compare view” feature, which enables you to visualize the changesets that are different between two forks. Compare view works for both incoming and outgoing changesets between a forked repository and it’s parent.

We’ve found this feature super useful, so we’ve added on new capabilities.

New Features

So how would you use this?

Imagine that you’ve been working on your own fork of a given project. You’ve made your changes, pushed to your fork on Bitbucket, and you’re now ready to request a pull into the master repository.

Using compare view on your own repository:

On the flip side, imagine you’re responsible for a project with many of contributors, each of whom might have one or more of their own forks. You can look at the full list of all forks of your repository. With one click you can see what changes are waiting in each repository for you to pull. After any merge conflicts are resolved, you know it’s safe to pull and merge between the two forks.

But wait, there’s more!

In addition to comparing between forks, you can also compare between tags and branches. Just look for the icon!

See it in action

Explore the feature for yourself, using the compare view pyflakes3k example we put up.

  • Anonymous

    hooray!!!1111

  • Anonymous

    hooray!!!1111

  • Anonymous

    hooray!!!1111

  • http://twitter.com/python_majibu python majibu

    Awesome, nice feature!!! Thanks

  • http://twitter.com/python_majibu python majibu

    Awesome, nice feature!!! Thanks

  • http://twitter.com/python_majibu python majibu

    Awesome, nice feature!!! Thanks

  • http://twitter.com/learnwell Pulkit

    I don’t see an option to select which of the files or commits to take over from source to another destination, it seems to be an all or nothing deal between the two branches.
    Is that a limitation or is there some way to control this?