Getting the current version of Satchmo
Satchmo has moved to using Mercurial for code hosting.
You can clone the repository using https:
$ hg clone https://email@example.com/chris1610/satchmo/
or, if you have setup your public ssh key,
$ hg clone ssh://firstname.lastname@example.org/chris1610/satchmo/
Using Mercurial For Satchmo Development
Prior to June 24, 2009 Satchmo was hosted on svn. On this date, we moved to mercurial in order to support a more open, flexible and collaborative development style. For those not familiar with using mercurial, here is a quick idea of how the development cycle could work.
1. Clone the latest version of the repository. In this example, I'm creating a satchmo-gold to hold the master repository.
$ hg clone https://bitbucket.org/chris1610/satchmo satchmo-gold
2. Create a separate local repository for the new feature you want to add. You can create as many of these as you need.
$ hg clone satchmo-gold satchmo-new-feature
3. Make changes to the files in satchmo-new-feature. Make sure to commit the changes. When you commit, you're only adding to the new-feature repository.
$ cd satchmo-new-feature/docs/ $ vi shipping.txt $ hg commit
4. Pull those changes back to the satchmo-gold repository. At this point we're assuming there are no merge conflicts.
$ cd ../../satchmo-gold $ hg pull ../satchmo-new-feature $ hg update
5. Inform the author by an easy or advanced way:
5a. Simple method:
- Export one or more changesets to a file and send it e.g. by e-mail as attachment.
$ hg export -r . -o ../patch1.txt
$ hg push ssh://email@example.com/your_user_name/satchmo
- Send pull request to the author by several clicks.
If you have configured
default-push url in
.hg/hgrc , you can submit simply by:
$ hg push
You find more in Contribute to Bitbucket projects using forks and pull requests.