Proprietary branch is publicly viewable!

Hi Mike,

Purchasing a subscription for a project does not automatically provision the project with privacy features. An administrator needs to gather some data from you and turn on the features you request.

It looks like you have deleted the branch which was pushed up as public -- good. If not please do so.

I have set up your project to have private codehosting with branches visible to the songwhaledevs team. No one but members of that team will be able to push to or see branches for your project.

You'll need to follow the link to 'Configure code hosting' off the front page of your project. Make sure you mark the branch for 'trunk' (or whatever you choose to call your current development branch) as owned by the songwhaledevs team. You'll be shown the bzr command for how to push to that branch.

Sorry for the bumpy start. Let me know if I can help further.

Mike for real-time help please join the #launchpad IRC channel on freenode.net, if you are familiar with using IRC.

Thanks, that was exactly what we were looking for. And thanks for the quick response.

We set up a second branch and tried to assign it to another team: songwhale ceti, however we got this message:

Oops!
Sorry, something just went wrong in Launchpad.

We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.

(Error ID: OOPS-1747ED661)

Do we need to do something special with that group in order to give it a private branch?

Hi Mike--

Since you've got some other questions related to this, I'm reopening it and moving it over to another team that can give you more specific help on branches.

Mike--

The default for the project is now forbidden; only members of the songwhaledevs team can work with the branches. You received that error because you were trying to create branches on the project without permission for that team. Thanks for giving us the OOPS code--I've filed a bug regarding it.

If you have other teams that are doing development work on songwhale and need access to the project code, you can add them as members to songwhaledevs; this will grant them access. Make sure any teams you add (e.g. songwhale ceti) have their Membership set to Restricted--you don't want anyone to be able to join a team that provides access to your code.

More documentation on this is available at https://help.launchpad.net/Code/PrivateBranches.

Let us know if we can help further.

Hi Mike,

The internal error there is

BranchCreationForbidden: You cannot create branches in "~songwhaleceti/songwhale"

Hi Mike,

Branch privacy is configured on a per-team basis. When I first helped you I set up ~songwhaledevs to have access to your project's private branches. Each top-level team you wish to have private branches needs to be configured -- it is a simple process, you just have to ask. I have just given the new team ~songwhaleceti access to the private branches.

The OOPS you saw was a bug in that you should have just been shown a message stating you didn't have permission to do what you were attempting.

If you try again you should be able to use the ~songwhaleceti team.