Feature #72

Feature #71: Track external repositories

Add option of tracking external repository to project settings

Added by Chris Cannam over 13 years ago. Updated over 13 years ago.

Status:ClosedStart date:2011-01-26
Priority:HighDue date:
Assignee:Luis Figueira% Done:

100%

Category:-
Target version:-

Description

In the project settings Repository tab, we currently have:

  • For a new project: a message saying that the repository will be created (so you should just wait for it), and a dropdown for the type of repository (in which Mercurial is the only option -- this dropdown is currently totally redundant)
  • Once the repository has been automatically created: a dropdown for the type of repository (now permanently set to Mercurial and greyed out, so still redundant); a "root directory" URL field (also greyed out and unchangeable); and a mysterious "Overwrite default settings..." check box which, although functional, is probably more confusing than useful.

What we want instead is something like:

  • For a new project: a message saying that the repository will be created; a check box saying "Track an external repository", with a description explaining that this means the local repository will be updated automatically and will be read-only; and a text field to enter the external repository URL enabled only if the "track" check box is checked.
  • Once the repository has been automatically created: exactly the same, but without the message saying the repository will be created. (None of the current repo settings are of any real use, are they?)

Thus, the "track external" check box and the external repo URL should be the only things presented as editable settings at all. The rest should maintain their default settings.

Also, we should remove the "Delete" link. It doesn't do anything useful -- it doesn't actually delete the repo from disc (thank goodness!) and the background daemon will just repopulate it into the settings again the next time it runs anyway.

Our model is different from the default Redmine one, the user has no control over their repo on the file system -- it always exists and always at the same location for any given project -- they just get to choose whether it's used for the project or not (through the Modules tab).

History

#1 Updated by Chris Cannam over 13 years ago

  • Status changed from New to Closed

Functionally complete, rolling back into parent task

#2 Updated by Chris Cannam over 13 years ago

  • % Done changed from 0 to 100

Also available in: Atom PDF