Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
Bugzilla:Git: Difference between revisions
Updating some URLs to match reality, and updating tag name to match new best practice.
(Add category) |
(Updating some URLs to match reality, and updating tag name to match new best practice.) |
||
| Line 1: | Line 1: | ||
The Bugzilla Project uses the [http://git-scm.com/ git] Version | The Bugzilla Project uses the [http://git-scm.com/ git] Version Control System. You can see the contents of the Bugzilla git repository on [http://git.mozilla.org/?p=bugzilla/bugzilla.git;a=summary Mozilla's git server]. | ||
= Checking Code Out of git = | = Checking Code Out of git = | ||
| Line 5: | Line 5: | ||
The simplest way to get the latest Bugzilla development code is: | The simplest way to get the latest Bugzilla development code is: | ||
git clone | git clone https://git.mozilla.org/bugzilla/bugzilla.git | ||
That will clone the Bugzilla git repository into a directory called "bugzilla" and will | That will clone the Bugzilla git repository into a directory called "bugzilla" and will check out the "master" branch. | ||
If you want other branches, in the bugzilla directory simply checkout another branch: | If you want other branches, in the bugzilla directory simply checkout another branch: | ||
| Line 14: | Line 14: | ||
git checkout 4.2 | git checkout 4.2 | ||
That will switch the files in the working directory to latest commit | That will switch the files in the working directory to latest commit on the 4.2 branch. Note that this doesn't necessarily correspond to the latest release in that series; additional patches may have been checked in since. | ||
== Getting A Specific Release == | == Getting A Specific Release == | ||
| Line 20: | Line 20: | ||
Every time we release a version of Bugzilla, we tag the git repository so that the point in history that matches with that release can be explicitly checked out of the repository. For example, to check out Bugzilla 4.1.3, you would do: | Every time we release a version of Bugzilla, we tag the git repository so that the point in history that matches with that release can be explicitly checked out of the repository. For example, to check out Bugzilla 4.1.3, you would do: | ||
git checkout | git checkout release-4.1.3 | ||
That will switch the files in the working directory to the commit released as version 4.1.3. | That will switch the files in the working directory to the commit released as version 4.1.3. | ||