Why would I want to use Mercurial or any other DVCS client with a Subversion repository?
- It lets us keep SVN as our central repository
- Some team members prefer not to use a DVCS for whatever reason so it lets them carry on using SVN without interruption.
- It allows me to work and commit changes (but not push!), search history and switch between branches completely disconnected. I can continue to work during network outages or while traveling when I don’t have connectivity.
- You get full, fast history search.
- Switching between branches is easy and fast.
- Any automated processes which use SVN (i.e. automated builds and deployments) can continue to operate while everyone moves to DVCS.
- It’s much easier to perform merges than regular SVN (via export/import patch queues – which I detail later)
I was having an issue where after pushing my changes to bitbucket, the changesets listed a different user as having pushed the files. For bitbucket, the commit username has to match your bitbucket username. As commits in Mercurial are local, we have no way of controlling that you have set your username correctly. It is important for you to set this up in such a way that we can identify your user account on Bitbucket when you push your commits to us.