# Renaming github repo from concrete5 to Concrete CMS

**URL:** https://forums.concretecms.org/t/renaming-github-repo-from-concrete5-to-concrete-cms/2129
**Category:** Developing with Concrete
**Created:** [January 11, 2022, 5:57pm UTC](https://forums.concretecms.org/t/renaming-github-repo-from-concrete5-to-concrete-cms/2129 "2022-01-11T17:57:20Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![mlocati](https://forums.concretecms.org/user_avatar/forums.concretecms.org/mlocati/32/6208_2.png) [@mlocati](https://forums.concretecms.org/u/mlocati)
#### Post date: [January 12, 2022, 8:58am UTC](https://forums.concretecms.org/t/renaming-github-repo-from-concrete5-to-concrete-cms/2129/3 "2022-01-12T08:58:03Z")

</div>

I’d suggest to rename the repository, and avoid creating a new clone of it.

Why? GitHub is very smart: when you rename a repository, every web and git request that use the old URL will be automatically redirected to the new one.

For example, I renamed [https://github.com/mlocati/login\_destination](https://github.com/mlocati/login_destination) to [https://github.com/concrete5-community/login\_destination](https://github.com/concrete5-community/login_destination) (see [How to move a GitHub repository to the concrete5-community organization - YouTube](https://www.youtube.com/watch?v=8ukInuYl5l8) to see how I did it).  
If you visit the old URL with the browser, you’ll be automatically redirected to the new one.  
And even `git clone https://github.com/mlocati/login_destination.git` still works.

---

_[View the full topic](https://forums.concretecms.org/t/renaming-github-repo-from-concrete5-to-concrete-cms/2129)._