To rename a GitHub repository, go to your repo's Settings tab, change the name in the "Repository name" field, and click "Rename." GitHub automatically redirects the old URL to the new one. However, renaming can break connections with Lovable, Vercel, and other tools that reference the old name — so update those integrations immediately after renaming.
What Happens When You Rename a Repository?
Renaming a GitHub repository changes its URL from github.com/your-name/old-name to github.com/your-name/new-name. GitHub is helpful here — it automatically sets up a redirect from the old URL to the new one, so links people have shared won't break immediately. However, this redirect only covers the GitHub website. External tools and services that store your repository name — like Lovable, Vercel, Netlify, or CI/CD pipelines — will not automatically pick up the new name. If you built your app with Lovable and it's synced to a GitHub repo, renaming that repo can break the two-way sync. The same goes for Vercel deployments that reference the repo by name. The rename itself is instant and reversible (you can rename again), but the ripple effects on connected tools need your attention.
Prerequisites
- A GitHub account with a repository you own
- Admin or owner permissions on the repository
- A web browser with internet access
Step-by-step guide
Open your repository's Settings page
Open your repository's Settings page
Navigate to your repository on github.com. Look at the row of tabs near the top of the page — you'll see "Code," "Issues," "Pull requests," and more. Click the "Settings" tab on the far right of that row. If you don't see a Settings tab, you don't have admin permissions on this repository. You'll need the repository owner to either rename it or grant you admin access. The Settings page opens to the "General" section by default, which is exactly where you need to be.
Expected result: You see the Settings page with the "General" section showing the "Repository name" field at the top.
Change the repository name
Change the repository name
At the top of the General settings page, you'll see a field labeled "Repository name" with your current repo name pre-filled. Click into this field and clear the existing name. Type your new repository name using lowercase letters, numbers, and hyphens — for example, change "my-old-project" to "fitness-tracker-app." Avoid spaces and special characters. GitHub will instantly check if the new name is available under your account and show a message if there's a conflict.
Expected result: The new name is typed into the field with no error messages about conflicts.
Click the Rename button to confirm
Click the Rename button to confirm
Once you've typed the new name, click the "Rename" button next to the field. GitHub may show a confirmation dialog warning you about the consequences of renaming. Read the warning carefully — it mentions that some features may take time to update. Click "I understand, let's rename this repository" (or similar confirmation text) to proceed. The rename takes effect immediately, and your browser's URL bar will update to show the new repository name.
Expected result: The page reloads with the new repository name in the URL and at the top of the page.
Verify the old URL redirects properly
Verify the old URL redirects properly
Open a new browser tab and type your old repository URL — for example, github.com/your-name/old-name. GitHub should automatically redirect you to the new URL. This redirect will keep working unless someone creates a new repository with the old name, which would break the redirect. Bookmark the new URL and update any links you've shared in documents, Notion pages, or Slack messages.
Expected result: Visiting the old URL redirects you to the new repository URL without any errors.
Update connected tools and services
Update connected tools and services
This is the most important step. If your repository is connected to external tools, you need to update them. For Lovable: the two-way GitHub sync may break after a rename — you may need to disconnect and reconnect the GitHub integration in Lovable's settings. For Vercel: go to your Vercel project settings and reconnect the Git repository if deployments stop working. For GitHub Desktop: the app should detect the rename automatically, but if it doesn't, remove and re-clone the repository. Check any Zapier or Make automations that reference the repository name and update them as well.
Expected result: All connected tools (Lovable, Vercel, CI/CD) are updated and working with the new repository name.
Complete working example
1# Fitness Tracker App23A workout tracking application built with Lovable and Supabase.45## Repository Renamed67This repository was renamed from `lovable-project-abc123` to `fitness-tracker-app`.89The old URL (github.com/janedoe/lovable-project-abc123) now redirects here.1011## Connected Services1213- **Lovable**: Reconnected after rename14- **Vercel**: Deployment URL updated15- **Supabase**: No changes needed (uses project ID, not repo name)1617## Tech Stack1819- React + TypeScript + Tailwind CSS20- Supabase (database + auth)21- Deployed on Vercel2223## License2425MITCommon mistakes when renaming a Repository on GitHub Without Breaking Anything
Why it's a problem: Renaming the repository without updating Lovable's GitHub connection
How to avoid: Open Lovable → Settings → Connectors → GitHub. Disconnect the old repo and reconnect using the new repository name.
Why it's a problem: Assuming all external services will follow the redirect
How to avoid: GitHub's redirect only works for web browsers visiting the URL. API calls, CI/CD pipelines, and deployment tools store the repo name separately and must be updated manually.
Why it's a problem: Creating a new repository with the old name after renaming
How to avoid: This breaks the automatic redirect. Avoid reusing the old name unless you specifically want to replace the redirect with a new project.
Why it's a problem: Renaming without admin permissions and wondering why Settings is missing
How to avoid: Only repository admins and owners can rename. Ask the owner to grant you admin access or to perform the rename.
Best practices
- Choose a permanent, descriptive name upfront to avoid needing to rename later
- Always update Lovable, Vercel, and other connected services immediately after renaming
- Keep a note of the old name so you can update shared links and documentation
- Avoid renaming repositories that are actively being developed by a team — coordinate first
- Never create a new repository with the old name unless you intentionally want to break the redirect
- Test your deployment pipeline after renaming to confirm everything still builds and deploys
- Update your README to mention the rename so collaborators aren't confused
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
I renamed my GitHub repository from [old-name] to [new-name]. What external services and integrations might break, and what steps should I take to update each one?
Frequently asked questions
Does renaming a GitHub repository break existing links?
Not immediately. GitHub sets up an automatic redirect from the old URL to the new one. However, the redirect breaks if someone creates a new repository with the old name. External tools like Lovable and Vercel store the repo name separately and must be updated manually.
Can I rename a repository back to its original name?
Yes, as long as no one has created a new repository using the old name. Just go back to Settings → General and change the name again.
Will renaming affect my Vercel deployment?
It can. Vercel references the repository by name in its Git integration. If deployments stop working after renaming, go to your Vercel project settings, disconnect the Git repo, and reconnect it with the new name.
Does renaming change the repository's clone URL?
Yes. The clone URL updates to reflect the new name. If you're using GitHub Desktop, it should detect the change automatically. If not, remove the repo from GitHub Desktop and re-clone it.
Will my Lovable project break if I rename the connected GitHub repo?
It may. Lovable's two-way sync references the repo name. After renaming, check Lovable's Settings → Connectors → GitHub and reconnect if the sync stopped working.
Can I rename a repository if I'm not the owner?
No. Only users with admin or owner permissions can rename a repository. If you're a collaborator, ask the owner to rename it or to grant you admin access.
Is there a way to rename without any risk of breaking things?
The safest approach is to create a new repository with the desired name and transfer your code there. For complex projects with many integrations, teams like RapidDev can help coordinate the migration to avoid downtime.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your project.
Book a free consultation