## page was renamed from Code/PersonalBranches/Draft
~-[[FrontPage|Launchpad Help]] > [[Code]] > Personal branches -~

||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||

= Overview =

Branches hosted by Launchpad are usually asssociated with a project.

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 [[https://code.launchpad.net/people/+me|your own branch list]]. 

However, there are some differences:

 * you can't propose a +junk branch for merging
 * 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 need to make the branch be owned by a team that both you and the other person are members of. Better still, when you are ready to collaborate, you should [[https://help.launchpad.net/Projects/Registering|create a project]] and move the +junk branch into the project.

= Creating a +junk branch =

Adding a +junk branch to Launchpad is the same as creating any other hosted branch. Instead of using the project name in the branch URL, you use +junk.

For instance: `bzr push ~matthew.revell/+junk/mybranch`

= Next step =

If you want to work on a project that uses an external Bazaar, git, CVS or Subversion branch to host its trunk line of development, you can ask Launchpad to [[Code/Imports|import it into a Bazaar branch]].

||<tablestyle="width: 100%;"> ~-[[Code/BugAndBlueprintLinks|< Linking branches to bug reports and blueprints]] -~ ||<style="text-align: right;"> ~- [[Code/Imports|Imports from Bazaar, git, Subversion and CVS >]] -~ ||