Iteration 1046

By on November 26, 2010

With Mercurial and other DVCSes, commits are performed locally before sharing with other developers. When making a local commit, you’re telling your local Mercurial repository, “I’m Bob and I have these changes”. The ownership of the changes then recorded and based on your ~/.hgrc configuration file.

When these changes are then pushed to Bitbucket or another Mercurial repository, the username information is used to determine the changeset ownership. When displaying the participants of these changesets on Bitbucket, we try our best to match on email first, second username, etc., but if there isn’t sufficient information, it’s very possible we may have linked the commit to someone else’s profile. Sorry. Please note that even if a changeset is mis-credited, that person cannot access your repository or your code.

Maybe you’ve seen this problem in your changeset history, when another user on Bitbucket is being given credit for code they didn’t participate in. We’ve heard your requests in the forums and in support and we have a solution.

Starting today, developers can provide custom username mappings for individual repositories. If a user switches email addresses, changes their name or even has a different hg configuration on another machine they use, Bitbucket can now help you with custom user aliasing.

Another change that we’re excited about is a revamp we’ve only begun to the Explore Bitbucket page. It’s one of the most popular pages on Bitbucket (3rd after login) and now (we think), one of the better looking pages.

With this revamp, you can now sort by the most followers or forks. Another change to the repository listing is that we’re taking advantage of a new repository language attribute we rolled out the other day. When creating a repository (or editing), you can now set your project language. Repositories that have set their project language will have this meta data added to their Explore repository listing. If you haven’t already noticed and set the attribute on your repositories, please do so or you’ll end up missing out later!




  • Posted November 26, 2010 at 12:44 am | Permalink

    These iteration blog posts are awesome — keem 'em coming! 🙂

  • Posted November 26, 2010 at 8:44 am | Permalink

    These iteration blog posts are awesome — keem ’em coming! 🙂

  • Posted November 26, 2010 at 8:44 am | Permalink

    These iteration blog posts are awesome — keem ’em coming! 🙂

  • Shrawan Patel
    Posted June 8, 2011 at 11:15 am | Permalink

    This post excellently highlights what the author is trying to communicate. Nonetheless, the article has been framed excellently well and all credits to the author. For more information on how to load balance your web servers, please visit ..n, n

One Trackback