git repository fork, needs to allow specifying information type, or at least use the highest one of the new owner
Bug #2011833 reported by
Dimitri John Ledkov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
git repository fork, needs to allow specifying information type, or at least use the highest one of the new owner
when forking a public git repository, into a private team, the new repository has information type public.
it should be the one that matches the new team (i.e. if the team is private new repository should have information type private).
Or the fork api call must accept information type setting, such that the new git repository has desired information type from creation.
Revision history for this message
| Jürgen Gmach (jugmac00) wrote | #1 |
| Changed in launchpad: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
To post a comment you must log in.
We had a quick discussion at our standup, and your request is certainly valid.
We have not come to a final conclusion what's the best way forward.
After some discussions, IMHO there are very few cases (if at all) where it makes sense that a private team has a public repository, so a private team forking a public repo should make the the repo private, too.