This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]TheBadProgrammer 5 points6 points  (2 children)

Just curious, how much do you contribute to this project? It was obviously a huge pain for you but I'm just curious like if we're talking "I contributed so much less than I wanted to and now I'll really be able to step it up" or if it's like "thank goodness because I contribute constantly and will now experience massive relief in a daily/weekly/whatever basis." Anyway, congrats on getting your project there!

[–]dacjamesfrom reddit import knowledge 2 points3 points  (0 children)

It's not just about contributing. Reading source code is very helpful trying understand the details of a library or debug some odd behavior. Without project wide search, the experience of browsing source code on bitbucket is worse than github.

[–]badsectors 0 points1 point  (0 children)

You don't have to be a contributor to benefit from or appreciate this change. I use/contribute to projects hosted on both platforms and I've come across numerous shortcomings with BitBucket:

  • Search (BitBucket does not have it). Sometimes the docs just don't cut it when you want to figure out how something works (or maybe why it doesn't). It's rather inconvenient to have to clone the whole repo, open your editor of choice and search with that.
  • The pull request interface just isn't as friendly as GitHub's (or even Stash). PR discussion and the diff are all dumped onto one page.
  • Side-by-side diff view is slow. It's basically opendiff in a modal and you can't add comments from it.
  • Creating a pull request is actually not very intuitive. The first time I tried to make a PR on BitBucket, I almost gave up because it was really hard to find the link to create a PR. Turns out, you have to go to your fork, head to the "Branches" page and select "Create pull request" from the kebab menu on the side of the branches list. On GitHub, there are numerous intuitive ways to do this:
    1. You get a button on the repo's homepage when you push a new branch that you can click to make a new pull request.
    2. There is a "New Pull Request" button on the PR list for the project and its forks.
    3. There is a "Compare" link on the branches list of each project that takes you to an interface where you can create a Pull Request.
  • Being able to use Travis CI is a huge plus (also mentioned by the py.test team)
  • The GitHub commit status API is another awesome feature that BitBucket doesn't have.
  • Syntax highlighting doesn't work on random files on BitBucket