bzr branch
http://gegoxaren.bato24.eu/bzr/brz/remove-bazaar
|
7206.2.1
by Jelmer Vernooij
Add support for --fixes in Git repositories. |
1 |
======================== |
2 |
Using Breezy with GitHub |
|
3 |
======================== |
|
4 |
||
5 |
GitHub: the largest code-hosting site |
|
6 |
------------------------------------- |
|
7 |
||
8 |
This tutorial looks at how Breezy and GitHub can be used together. |
|
9 |
||
10 |
Accessing code in GitHub using Breezy |
|
11 |
======================================== |
|
12 |
||
13 |
Getting the code for a project |
|
14 |
------------------------------ |
|
15 |
||
16 |
Breezy users can grab code from GitHub using regular GitHub URLs: |
|
17 |
||
18 |
brz branch git://github.com/owner/name |
|
19 |
||
20 |
where `owner` is the name of the owner and `name` is the repository name. Here are some examples:: |
|
21 |
||
22 |
brz branch https://github.com/inkscape/inkscape |
|
23 |
brz branch git://github.com/KDE/amarok |
|
24 |
brz branch https://github.com/python/cpython |
|
25 |
||
26 |
You can then browse the code locally using your favorite editor or IDE and |
|
27 |
change the code if you wish. |
|
28 |
||
29 |
To access a non-default branch, specify the 'branch' segment parameter:: |
|
30 |
||
31 |
brz branch https://github.com/inkscape/inkscape,branch=backports |
|
32 |
||
33 |
Publishing your changes |
|
34 |
----------------------- |
|
35 |
||
36 |
Having fixed that annoying bug or added that cool feature you've always |
|
37 |
wanted, it's time to impress your friends and make the world a better |
|
38 |
place by making your code available to others. As explained earlier, |
|
|
7206.2.2
by Jelmer Vernooij
Review comments. |
39 |
GitHub is a code hosting service so you can push your |
40 |
branch to it and others can access your code from there. |
|
41 |
||
|
7490.9.1
by Jelmer Vernooij
Document the 'brz publish' command. |
42 |
The first time you use GitHub, you will need to log into to your GitHub account |
43 |
with Breezy. This can be done by running ``brz github-login``. This will prompt |
|
44 |
you for your password, and store the authentication token in ~/.config/breezy. |
|
45 |
||
46 |
You can now use either ``brz publish`` to upload the changes back to |
|
47 |
GitHub, or ``brz propose`` to upload to the changes to GitHub and |
|
48 |
create merge proposal. |
|
49 |
||
50 |
Both ``brz publish`` and ``brz propose`` will create a fork of the upstream |
|
51 |
repository and then push your local changes to the active branch |
|
52 |
(or another branch specify with the --name argument). |
|
53 |
||
54 |
For example, running ``brz publish --name=my-branch`` in your local inkscape |
|
55 |
clone will create https://github.com/jelmer/inkscape if your GitHub username is |
|
56 |
"jelmer", and it will open your editor to allow you to enter the merge proposal |
|
57 |
description. |
|
58 |
||
59 |
Subsequent use of ``brz publish`` in the local branch (e.g. to push more |
|
60 |
commits) will update the previously created branch. |
|
|
7206.2.1
by Jelmer Vernooij
Add support for --fixes in Git repositories. |
61 |
|
62 |
Associating branches with GitHub issues |
|
63 |
--------------------------------------- |
|
64 |
||
65 |
The standard Breezy bugtracking functionality can also be used for GitHub |
|
66 |
issues. |
|
67 |
||
68 |
When you commit using Breezy, use the --fixes option like this:: |
|
69 |
||
|
7206.2.2
by Jelmer Vernooij
Review comments. |
70 |
brz commit --fixes github:inkscape/inkscape/1234 |
|
7206.2.1
by Jelmer Vernooij
Add support for --fixes in Git repositories. |
71 |
|
72 |
where 1234 is the bug ID. This will add some metadata to the commit message. |
|
73 |
||
74 |
You can also define a short name for a specific project, by adding an alias for |
|
75 |
a project. For example, to add an alias for dulwich:: |
|
76 |
||
77 |
brz config bugtracker_dulwich_url=https://github.com/dulwich/dulwich/issues/{id}
|