To create a new repository on GitHub, click the green "New" button on your dashboard or go to github.com/new. Give your repo a name, add a description, choose public or private, check "Add a README file," and click "Create repository." The whole process takes under a minute and requires zero coding.
What Is a GitHub Repository?
A repository (often called a "repo") is a folder on GitHub that holds all the files for a single project. Think of it like a project folder on your computer, except GitHub tracks every change ever made to every file — so you can always go back to a previous version. Repositories can be public (anyone can see them) or private (only people you invite can see them). When you use AI app builders like Lovable or V0, they create repositories to store the code they generate. Understanding how to create and configure a repository yourself gives you control over where your project lives and who can access it.
Prerequisites
- A GitHub account (free plan works)
- A web browser with internet access
- A project name in mind
Step-by-step guide
Navigate to the new repository page
Navigate to the new repository page
Log in to github.com. On your dashboard, look for the green "New" button in the left sidebar next to the word "Repositories." Click it. Alternatively, you can go directly to github.com/new in your browser's address bar. Both paths take you to the same "Create a new repository" form. The page has several fields and checkboxes — don't worry, most have sensible defaults.
Expected result: You see the "Create a new repository" form with fields for owner, name, and description.
Choose an owner and repository name
Choose an owner and repository name
The "Owner" dropdown shows your username (and any organizations you belong to). Leave it set to your personal account for now. In the "Repository name" field, type a short, descriptive name using lowercase letters and hyphens — for example, "my-landing-page" or "workout-tracker-app." GitHub will instantly check if the name is available and show a green checkmark if it is. Avoid spaces, uppercase letters, and special characters.
Expected result: A green checkmark appears next to your repository name confirming it's available.
Add a description and choose visibility
Add a description and choose visibility
Below the name field, type a one-sentence description of your project — for example, "A workout tracking app built with Lovable and Supabase." This description appears on your repository's page and in search results. Next, choose your visibility: select "Public" if you want anyone to see your code, or "Private" if you want to restrict access. For most personal projects, private is the safer choice. You can always change this later in the repository settings.
Expected result: Your description is filled in and either Public or Private is selected.
Initialize with a README file
Initialize with a README file
Scroll down to the "Initialize this repository with" section. Check the box that says "Add a README file." A README is a text file that appears on your repository's homepage — it's like a cover page for your project. This checkbox is important because it creates an initial file in your repo, which means you can immediately start adding more files through the web interface. Without it, you'd get an empty repository with setup instructions that require the command line.
Expected result: The "Add a README file" checkbox is checked.
Optionally add a .gitignore and license
Optionally add a .gitignore and license
Below the README checkbox, you'll see two dropdown menus. The ".gitignore template" dropdown lets you pick a template that tells GitHub to ignore certain files (like temporary files or system files). If you're building with Lovable or V0, select "Node" from the dropdown since those tools use Node.js. The "License" dropdown lets you add an open-source license. For private projects, you can skip the license. For public projects, "MIT License" is the most common and permissive choice.
Expected result: Your .gitignore is set to Node (optional) and a license is selected (optional).
Click Create repository
Click Create repository
Review your settings one more time: name, description, visibility, README checkbox. When everything looks right, click the green "Create repository" button at the bottom of the form. GitHub will create your repository and redirect you to its homepage. You'll see your README.md file displayed as the main content of the page, along with your description below the repository name. The repository is now ready to receive files — either uploaded manually or pushed automatically by AI tools like Lovable or Cursor.
Expected result: You land on your new repository's homepage showing the README.md content.
Complete working example
1# My Project Name23A brief description of what this project does.45## Tech Stack67- Built with [Lovable](https://lovable.dev) (AI app builder)8- Backend: Supabase (PostgreSQL + Auth)9- Deployed on Vercel1011## Getting Started1213This project was generated by an AI tool. To make changes:141. Open the project in Lovable152. Describe the changes you want163. Lovable will update the code and push to this repo1718## Project Structure1920- `src/` — Application source code21- `src/components/` — React components22- `src/pages/` — Page components23- `public/` — Static assets2425## License2627MITCommon mistakes when creating a New Repository on GitHub (Web UI Walkthrough)
Why it's a problem: Not checking "Add a README file"
How to avoid: Without a README, you get an empty repo with terminal-only setup instructions. If you forgot, click "Add file" → "Create new file" on the repo page and name it README.md.
Why it's a problem: Using spaces or special characters in the repository name
How to avoid: Use only lowercase letters, numbers, and hyphens. GitHub will auto-convert spaces to hyphens, but it's cleaner to type them yourself.
Why it's a problem: Accidentally creating a public repository for a private project
How to avoid: Go to the repository's Settings tab → scroll to Danger Zone → "Change repository visibility" → Switch to private.
Why it's a problem: Creating the repository under an organization instead of your personal account
How to avoid: Check the Owner dropdown before clicking Create. You can transfer the repo later in Settings → Danger Zone → Transfer ownership.
Best practices
- Always add a README file when creating a new repository
- Use lowercase letters and hyphens for repository names
- Write a one-sentence description that explains what the project does
- Start with a private repository and make it public later if needed
- Add a .gitignore file matching your tech stack to keep the repo clean
- Name repositories after the project, not the tool used to build it
- Add a license file for any public repository you plan to share
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
I just created a GitHub repository for my project. Write me a detailed README.md that explains the project is a [describe your app] built with Lovable and Supabase. Include sections for Tech Stack, Getting Started, and Project Structure.
Frequently asked questions
How many repositories can I create on a free GitHub account?
Unlimited. GitHub's free plan allows unlimited public and private repositories with no restrictions on the number of files or collaborators.
What is the difference between a public and private repository?
A public repository is visible to everyone on the internet. A private repository is only visible to you and collaborators you explicitly invite. Both are free on GitHub.
Can Lovable or V0 create a repository for me automatically?
Lovable can export your project to a new GitHub repository when you connect your GitHub account in Settings → Connectors. V0 creates a branch on an existing repo when you connect via the Git panel.
What is a .gitignore file?
A .gitignore file tells GitHub which files to ignore — like temporary files, build outputs, or sensitive files like .env. The Node template is a good default for JavaScript and TypeScript projects.
Can I rename a repository after creating it?
Yes. Go to the repository's Settings tab and change the name in the "Repository name" field at the top. GitHub will redirect the old URL to the new one automatically.
Can RapidDev help me organize my GitHub repositories?
Yes. RapidDev helps non-technical founders structure their GitHub repos, set up proper branching strategies, and connect repositories to AI build tools and deployment platforms.
Should I create one repository per project or put everything in one repo?
Create one repository per project. This keeps your files organized, makes it easier to connect to AI tools, and lets you manage permissions separately for each project.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your project.
Book a free consultation