39
39
GitHub is a code hosting service so you can push your
40
40
branch to it and others can access your code from there.
42
In the GitHub web UI, you can create a "fork" of an upstream repository. For
43
example, if user "jelmer" forked the inkscape repository at
44
https://github.com/inkscape/inkscape then the fork would be at
45
https://github.com/jelmer/inkscape.
47
You can then push your changes to a branch like this::
49
brz push git+ssh://github.com/jelmer/inkscape,branch=my-branch
51
Others can then download your code like this::
53
brz branch git://github.com/jelmer/inkscape,branch=my-branch
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.
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.
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).
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
59
Subsequent use of ``brz publish`` in the local branch (e.g. to push more
60
commits) will update the previously created branch.
56
62
Associating branches with GitHub issues
57
63
---------------------------------------
added
removed
doc/en/tutorials/using_breezy_with_github.txt
