Project

General

Profile

Git-maus » History » Version 22

Dobbs, Adam, 24 February 2017 18:30

1 1 Dobbs, Adam
h1. Git-maus
2
3 5 Dobbs, Adam
Besides Launchpad and bazaar MAUS has beta level support for git and"github":https://github.com/mice-software/maus. At the moment code updates for the trunk cannot be accepted from github however, only via Launchpad and bazaar.
4 1 Dobbs, Adam
5
h2. Development
6
7 2 Dobbs, Adam
h3. Set up a development branch
8
9 12 Dobbs, Adam
* Set up an account on "github":https://github.com/ and "add an ssh key":https://help.github.com/articles/connecting-to-github-with-ssh/ to your account
10
* Clone the MAUS repository as described at [[Install#Git-and-GitHub-beta-support| Obtaining MAUS via Git]]
11 2 Dobbs, Adam
* Fork the MAUS repository on github
12 19 Dobbs, Adam
** Go to "MAUS github page":https://github.com/mice-software/maus and login into github
13 2 Dobbs, Adam
** Click "Fork" in the top right of the screen, selecting the option to fork to your own account
14 18 Dobbs, Adam
15 21 Dobbs, Adam
16 20 Dobbs, Adam
    !http://micewww.pp.rl.ac.uk/attachments/8360/GitHubForkScaled.png!
17 21 Dobbs, Adam
18 18 Dobbs, Adam
19 22 Dobbs, Adam
** Select your own account from the options that appear for where to fork MAUS
20 2 Dobbs, Adam
* Add your fork as a new remote in your local MAUS git repository
21
** Copy the address of your new fork from github (something like @git@github.com:jbloggs/maus.git@, where jbloggs is your github username)
22
** Return to the terminal and navigate to the MAUS git repository created earlier
23
** Add your new forked repository using:
24
<pre>
25
git remote add my-fork git@github.com:jbloggs/maus.git
26
</pre>
27
where jbloggs is your github username.
28
* Fork the merge branch locally:
29
<pre>
30
git checkout merge
31
git checkout -b my-feature-branch
32
</pre>
33
* Push your local fork of the merge branch to your remote repository:
34
<pre>
35
git push my-fork my-feature-branch
36
</pre>
37
* Do some coding
38
* When ready add the files you have modified or created ready for committing:
39
<pre>
40
git add <files>
41
</pre>
42
* Commit your changes:
43
<pre>
44
git commit -m 'Some informative message about the changes'
45 1 Dobbs, Adam
</pre>
46 3 Dobbs, Adam
* Push the changes to your remote repository:
47
<pre>
48
git push my-fork my-feature-branch
49
</pre>
50
51
h3. Propose your branch for merging
52
53
* Run Jenkins test server job on your development branch (email the head of MAUS for help with setting up a test branch)
54
* When Jenkins has passed, return to your repository page on github and select @my-feature-branch@ from the drop-down menu on the left
55
* Click the "Pull request" button to propose merging into the trunk
56
* Make sure your branch is comfortable for merging - if not, edit some more until it is, commit and push, then try again