2320
Comment: h&f
|
2082
Mention Git in the imports link at the bottom.
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
## page was renamed from Code/PersonalBranches/Draft | |
Line 18: | Line 19: |
* only individuals - not teams - can register them | |
Line 29: | Line 29: |
Visit your [[https://code.launchpad.net/people/+me/+addbranch|register a branch]] page and make sure you: * select the ```Hosted``` option, to host the branch on Launchpad * do not enter a project name. |
Visit your [[https://code.launchpad.net/people/+me/+addbranch|register a branch]] page and make sure you select the ```Hosted``` option, to host the branch on Launchpad. |
Line 36: | Line 33: |
```~matthew.revell/+junk/mybranch``` ||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">{{attachment:my-junk.png}}|| ||<style="text-align: center;">'''A junk branch location'''|| |
{{{ ~matthew.revell/+junk/mybranch }}} |
Line 43: | Line 39: |
Informal support happens in many different places in the free software world. Launchpad aims to bring bug tracker-like qualities to giving and asking for help. Let's look at [[Answers|Launchpad Answers]]. | 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]]. |
Line 45: | Line 41: |
||<tablestyle="width: 100%;"> ~-[[Code/BugAndBlueprintLinks|< Linking branches to bug reports and blueprints]] -~ ||<style="text-align: right;"> ~- [[Answers|Answers >]] -~ || | ||<tablestyle="width: 100%;"> ~-[[Code/BugAndBlueprintLinks|< Linking branches to bug reports and blueprints]] -~ ||<style="text-align: right;"> ~- [[Code/Imports|Imports from CVS, Subversion and Git >]] -~ || |
Launchpad Help > Code > Personal branches
Contents |
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
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 import it into a Bazaar branch.