# Build 1870 - Renaming Repositories doesn't change existing $Repository.XYZoldname$ variables to $Repository.NewName$

**URL:** https://www.finalbuilder.com/forums/t/build-1870-renaming-repositories-doesnt-change-existing-repository-xyzoldname-variables-to-repository-newname/5808
**Category:** Bugs
**Created:** [April 15, 2013, 9:56am UTC](https://www.finalbuilder.com/forums/t/build-1870-renaming-repositories-doesnt-change-existing-repository-xyzoldname-variables-to-repository-newname/5808 "2013-04-15T09:56:45Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Jenasys](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/jenasys/32/888_2.png) [@Jenasys](https://www.finalbuilder.com/forums/u/Jenasys)
#### Post date: [April 15, 2013, 9:56am UTC](https://www.finalbuilder.com/forums/t/build-1870-renaming-repositories-doesnt-change-existing-repository-xyzoldname-variables-to-repository-newname/5808/1 "2013-04-15T09:56:45Z")

</div>

I'm not sure this is a bug or a feature, but as I'm adding the 50+ repo's I work with, the naming convention I'm working with has evolved as I've started to realise the extent of Automated builds possible with a DVCS.

Firstly, when I change some of the repositories names, Continua didn't then automatically change the old reference to the new reference within the existing project configurations I was using. Manually change was required.&nbsp; AKA. I had to find all the references to $Repository.xyz$ and change them.

Secondly cloning&nbsp;configurations and referencing a different&nbsp;"single" repository also requires you to step through every part of a configuration and ensure you are using the new repository.&nbsp; Again, it might be nice if Continua alerted you of the issue or, let the user decide if you want to automatically change the repository reference.