Product setup instructions
Create a private repository on GitHub, clone it to your computer, and push a verified first change.
Creator responsibility
We are responsible for the accuracy, safety warnings, compliance, and suitability of these instructions for the identified product.
Before you start
Sign in to github.com. Open Terminal, PowerShell, or Git Bash and run git --version.
Do not paste access tokens, passwords, or private SSH keys into a repository or terminal command shared by someone else.
GitHub account, web browser, Git, and a terminal
Git reports a version number and GitHub opens while you are signed in.
Select the plus menu, choose New repository, enter demo-notes as the name, choose Private, and select Add a README file. Select Create repository.
Use Public only when the repository contents are intended to be visible to everyone.
GitHub opens the demo-notes repository and displays README.md.
On the repository page, select Code, select HTTPS, then use the copy button beside the URL.
The copied address ends with /demo-notes.git.
In the terminal, change to your projects folder, run git clone followed by the copied HTTPS URL, then run cd demo-notes.
If a demo-notes folder already exists, choose another parent folder or remove the old clone only after confirming it contains no uncommitted work.
The demo-notes folder contains README.md and git status reports the main branch.
Add one line to README.md, save it, then run git add README.md and git commit -m "Update README".
A commit records the staged change locally. It does not update GitHub until it is pushed.
git status reports that the working tree is clean.
Run git push origin main. Return to the repository page in GitHub and refresh it.
If Git asks you to authenticate, use Git Credential Manager, GitHub CLI, or an SSH key. GitHub does not accept an account password for Git operations.
GitHub shows the Update README commit and the new README line.
Manual complete
The GitHub repository has a local clone, a recorded commit, and a verified remote copy.