Development/Git: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
No edit summary
No edit summary
Line 18: Line 18:
== Help ==
== Help ==


Confused? Send an email to support@musicbrainz.org if you need more help, or drop by the IRC channel at irc://irc.freenode.net/musicbrainz. Additionally, check out the Contact Us page for more ways to get in touch.
Confused? Send an email to support@musicbrainz.org if you need more help, or drop by the [[IRC|IRC channel]]. Additionally, check out the [[Contact Us]] page for more ways to get in touch.


== Development with Git ==
== Development with Git ==
Line 28: Line 28:
git checkout -b my-cool-feature master
git checkout -b my-cool-feature master


When you are ready to share your work with us you have a few options - if you wish to submit a patches, you should use [http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html git format-patch]. These can then be emailed to the [[Developers Mailing List|developers mailing list]]. If you're doing work on more than one branch, or you'd like to have more control we are happy to give you a branch or repository on git.musicbrainz.org to push work to. For more information on this, please ask the list and someone will give you more details.
When you are ready to share your work with us you have a few options - if you wish to submit a patches, you should use [http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html git format-patch]. These can then be emailed to the [[Developers Mailing List|developers mailing list]]. If you're doing work on more than one branch, or you'd like to have more control we are happy to give you a branch or repository on [http://git.musicbrainz.org git.musicbrainz.org] to push work to. For more information on this, please ask the list and someone will give you more details.


== Git Resources ==
== Git Resources ==
Line 37: Line 37:
* [http://kernel.org/pub/software/scm/git-core/docs/everyday.html Everyday GIT With 20 Commands Or So]
* [http://kernel.org/pub/software/scm/git-core/docs/everyday.html Everyday GIT With 20 Commands Or So]
* [http://www.spheredev.org/wiki/Git_for_the_lazy Git for the lazy]
* [http://www.spheredev.org/wiki/Git_for_the_lazy Git for the lazy]

[[Category:Development]] [[Category:Server]]

Revision as of 23:16, 8 February 2010

This page describes how to use the MusicBrainz Git repository.

Introduction

The latest stable and development versions of MusicBrainz Server are hosted on Git, at git.musicbrainz.org. You can browse the code through the web interface, and also clone each of these repositories for read only access. All releases we make are tagged on the master tree, and you can clone these to run stable released versions of MusicBrainz.

Checking out source code

To check out source code from our repository use this command:

git clone git://git.musicbrainz.org/musicbrainz-server/core.git mb_server

This will clone the latest master branch -- see the README for more information.

To stay up to date with late changes, just use git pull like so:

git pull

Help

Confused? Send an email to support@musicbrainz.org if you need more help, or drop by the IRC channel. Additionally, check out the Contact Us page for more ways to get in touch.

Development with Git

If you want to help contribute to MusicBrainz - it's really simple! All you need to do is branch off master and commit there:

git clone git://git.musicbrainz.org/musicbrainz-server/core.git mb_server
cd mb_server
git checkout -b my-cool-feature master

When you are ready to share your work with us you have a few options - if you wish to submit a patches, you should use git format-patch. These can then be emailed to the developers mailing list. If you're doing work on more than one branch, or you'd like to have more control we are happy to give you a branch or repository on git.musicbrainz.org to push work to. For more information on this, please ask the list and someone will give you more details.

Git Resources

If you're new to Git, don't worry - there is plenty of excellent documentation about how to use it: