Diff for "Code/PersonalBranches"

Not logged in - Log In / Register

Differences between revisions 10 and 11
Revision 10 as of 2009-08-10 00:03:05
Size: 2082
Editor: c122-108-27-22
Comment: Mention Git in the imports link at the bottom.
Revision 11 as of 2009-08-28 15:06:15
Size: 2024
Editor: 92-237-59-186
Comment:
Deletions are marked like this. Additions are marked like this.
Line 39: Line 39:
If you want to work on a project that use CVS or Subversion to host its trunk line of development, you can ask Launchpad to [[Code/Imports|import it into a Bazaar branch]]. You can work with Bazaar branches in Launchpad even if they're hosted elsewhere by [[Code/MirroredBranches|mirroring them]].
Line 41: Line 41:
||<tablestyle="width: 100%;"> ~-[[Code/BugAndBlueprintLinks|< Linking branches to bug reports and blueprints]] -~ ||<style="text-align: right;"> ~- [[Code/Imports|Imports from CVS, Subversion and Git >]] -~ || ||<tablestyle="width: 100%;"> ~-[[Code/BugAndBlueprintLinks|< Linking branches to bug reports and blueprints]] -~ ||<style="text-align: right;"> ~- [[Code/MirroredBranches|Mirrored branches >]] -~ ||

Launchpad Help > Code > Personal branches

Overview

Usually, when you register a Bazaar branch with Launchpad, you tell Launchpad which project the branch is associated with.

If you'd prefer to upload a branch to Launchpad without it showing up in any project's branch listings, you can use the +junk pseudo-project. This can be useful if your branch is:

  • for a project not yet in Launchpad
  • not ready to be publicly associated with a project.

+junk branches work in a similar way to normal branches: anyone can create their own branch and they show up in your own branch list.

However, there are some differences:

  • you can't propose a +junk branch for merger
  • they don't show up in any project's branch listing
  • you don't earn karma from +junk branches.

If you want to collaborate on a +junk branch with someone else, you'll need to create a project.

Registering a +junk branch

Adding a +junk branch to Launchpad is similar to registering a branch associated with a project.

Visit your register a branch page and make sure you select the Hosted option, to host the branch on Launchpad.

At top of the page, you'll see that the automatically updating branch name looks something like:

~matthew.revell/+junk/mybranch

Next step

You can work with Bazaar branches in Launchpad even if they're hosted elsewhere by mirroring them.

< Linking branches to bug reports and blueprints

Mirrored branches >

Code/PersonalBranches (last edited 2012-06-28 06:34:40 by wgrant)