1804
Comment: converted to 1.6 markup
|
← Revision 11 as of 2009-08-28 14:54:40 ⇥
33
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
You can host a Bazaar branch for any project that is registered in Launchpad. '''Before you start:''' you must have registered an SSH key in your Launchpad account. To register a key, visit http://launchpad.net/people/+me/+editsshkeys == Pushing your branch == To create your branch, use {{{bzr push}}}. The push location should be of the form: {{{bzr+ssh://}}}''login''{{{@bazaar.launchpad.net/~}}}''registrant''{{{/}}}''project''{{{/}}}''branch'' === Push location explained === * ''login'' is your Launchpad account name (or Launchpad ID): the last part of the URL of your Launchpad profile page. Launchpad uses it to check the SSH key you are authenticating with. * ''registrant'' is your Launchpad person name, or the name of a team you belong to. Use a team name to create a branch to which other members of that team can upload. * ''project'' is the name of the Launchpad project to register this branch on. The uploaded branch will appear in the listings for this project. * ''branch'' must be unique for a given registrant and project, and should describe the sort of change being done in that branch. For instance, "rework-decorator-API", or "fix-bug-42123", or "improve-timeout-warning". == If you don't have a project to push that branch to == If you are working on an actual open source project, you should register the project first: https://launchpad.net/projects/+new-guided -- but if it's just an experiment, or throwaway code, you can host it using Launchpad's NonProjectBranches. == Learn more == Using Bazaar with Launchpad is explained in more detail on FeatureHighlights/EasyBranching. Setting up and using team branches to allow multiple people to commit to a single branch is explained on FeatureHighlights/TeamBranches. |
#redirect Code/UploadingABranch |