2

We are thinking that our current repository layout may not be ideal as there are too many repositories and some things really ought to be moved together into the same repository.

Doing a force push and merge of the repos easily lets us combine them, but the problem is that if we then delete the original repos we can end up disrupting a lot of people until we get everyone switched over.

How can we go about reorganizing our repository layout in the least painful way possible?

flag

1 Answer

3

If I understand the problem right, I think, repository aliases could help to solve your problem.

EDIT :
Although, if you want to have such handy possibility, whenever it will be needed, you should add aliases for each repository all the time and work only with aliases. Otherwise, you need to fix the path to a repository for each person who works with the obsolete repository anyway.

link|flag
While you're correct that you'd want to use aliases to always have that ability, you probably don't want to do that. Kiln Alpha went to great lengths to ensure your old URLs would never break...and it ended up seriously biting a lot of customers really badly. This would be deliberately setting yourself up for the same. – Benjamin Pollack Aug 31 2010 at 20:29
Benjamin, I agree that it's not the best idea to manage all URLs of all repositories in fact manually. Personally, I don't want to deal with such mess of URLs. But, I've just pointed out the way to deal with the problem and sacrifice which you have to make to go this way. – Anton Moiseev Aug 31 2010 at 20:45

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.