Launchpad itself

Uploading multiple git repos to a project is confusing

Bug #1689369 reported by Alistair Buxton
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

To reproduce:

1. Create a new project.
2. Import a git repo to it.
3. Check the Code tab:

    - the repo you just uploaded is called "lp:project-name" regardless of what you entered in the repo name field when creating the repo and it has clone url "https://git.launchpad.net/project-name"

4. Import another repo.
5. Check the code tab again:

Result:

The first uploaded repo has it's name and clone URL changed. The second repo takes on the name lp:project-name and the "https://git.launchpad.net/project-name" clone URL.

This can be repeated multiple times. Each imported repo will push the previous one to a different URL.

6: Delete the most recent uploaded repo.

Result:

The repo disappears and now you have no repo called "lp:project-name" at all, until you import another one.

What should actually happen:

There should be an option like "owner default" except it should say "project default" and it should control which repo, if any, occupies the "lp:project-name" and "https://git.launchpad.net/project-name". Even better, just kill the idea of project default repo entirely, and make repos have consistent names.

Revision history for this message
Alistair Buxton (a-j-buxton) wrote :

Note that the "owner default" textbox has the label which says:

    "Whether this repository is the default for its owner and target."

But ticking it has no effect on the target default repo, if the target is a project.

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

We won't be killing the idea of a project default repository; it's a core part of Launchpad's git layout, and very useful in other contexts. You've gone a few steps too far in your diagnosis as a result of being confused by the UI, I think.

It is already possible to 'control which repo, if any, occupies the "lp:project-name" ...' slot. https://code.launchpad.net/PROJECT/+configure-code has a "Link to a Git repository already on Launchpad" option which does exactly that. However, that's not really the root of the UI confusion here.

Stepping back a bit, the point where things started to go wrong for you was that you found yourself on the UI page that's designed specifically for importing a project's default repository, rather than https://code.launchpad.net/+code-imports/+new which lets you import additional non-default repositories. I accept that this is confusing, and we need to either let you select what you want more explicitly or at least give you a link to the other page.

(And yes, the "owner default" UI could use some work too. Perhaps this should be redesigned as a set of radio buttons or similar, and it should explicitly tell you what the result is going to be in terms of URLs.)

tags: added: confusing-ui git lp-code ui
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Alistair Buxton (a-j-buxton) wrote :

Yes, you nailed it, thanks :)

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

Other bug subscribers

Remote bug watches

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