default repo for git merge should be based on parent repo

Bug #1784587 reported by Tom Haddon
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Some projects on LP can have multiple git repos (code branch, config branch, charm layer branch, etc.). Currently any merge proposal for a project defaults to the nominated repo for that project, but it would be useful if it defaulted to the parent repo it was created from.

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

Unfortunately we don't currently store that information, so heuristics are the best we can do.

tags: added: code-review git lp-code
Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
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.