Topic 2
Create Repository
Start from an empty private repository so the first push stays simple and the initial history is easy to understand.
Outcome
An empty private GitHub repository exists for the manuscript project.
Before you start
- The intended GitHub account is signed in.
- A unique repository name and visibility choice are decided.
Verification state
- Status
- Needs review
- Environment
- GitHub web interface; screenshots use the desktop Windows browser path.
- Workflow
- Creating an empty private repository without generated starter files.
- Last verified
- Pending a current GitHub UI walkthrough.
- Operating-system support
- Browser workflow is platform-independent; screenshots document the desktop path only.
Choose the repository shape
One private repository for one project is enough for the first workflow. Avoid adding extra files or automation until after the first push.
Create an empty private repository
Create a new private repository with a clear project name. Skip the README, .gitignore, and license to keep the first push flow explicit.
From your profile, open the repositories list first.
Then use the New button from that repositories page to start the repository form.
Choose a clear name, keep the repository private, and fill out only the basic form fields for the first run.
After creation, you should see an empty repository page ready for the first clone and push.
If the private repository exists on GitHub and is still empty, you are ready to clone it locally.
Common problems
- Preselecting a README creates remote history that complicates the first push from an existing local project.
- Repository visibility should be confirmed before uploading unpublished research material.
Completion check
The repository page shows the chosen name, Private visibility, and no generated README, license, or .gitignore commit.