No way to assign write permissions to a repository for a bot via +sharing

Bug #1722280 reported by Tom Haddon
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Undecided
Colin Watson

Bug Description

Currently the only way to let a bot make changes to a repository for you is to have it be a member of the team that owns the branch. If that team happens to have extensive privileges that means giving the bot those same privileges.

Revision history for this message
Colin Watson (cjwatson) wrote :

We fixed this early last year (via a separate "Manage permissions" view; +sharing is only for read permissions):

  https://blog.launchpad.net/code/git-per-branch-permissions

Changed in launchpad:
assignee: nobody → Colin Watson (cjwatson)
status: New → Fix Released
Revision history for this message
Colin Watson (cjwatson) wrote :

Note that this is only for git. It's somewhat unlikely that we'll be putting the amount of effort into bzr-related changes that would be needed to support the equivalent there too, and the problem was much more pressing for git given the multiple-branches-per-repository model.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.