So you wrote something that actually works and now you want to shove it up to GitHub without starting a small war. This guide walks you through a no nonsense git push workflow that keeps history tidy and your future self less angry. It is short, accurate, and lightly sarcastic for flavor.

Get a local repo ready

If your project is not yet tracked by git do this from the project folder. It creates a hidden history vault that remembers every regrettable change.

git init
git remote add origin REPO_URL

Replace REPO_URL with the address GitHub gives you. You can use SSH or HTTPS depending on what you prefer for authentication. We will talk about that below.

Stage and commit like a civilized human

Staging picks which files join the party. Committing records why you made the mess in the first place.

git add .
git commit -m 'Short tidy message about the change'

• Use git add file when you want to be picky.
• Keep commit messages concise and useful so future you does not cry.

Push your branch to GitHub

Once your local branch looks sane push it up.

git push -u origin main

The -u flag links your local branch to the remote so future pushes are one word simpler. If your main branch uses a different name replace main with the correct branch name.

Authentication options that will save you from typing your password forever

Pick one of these and set it up once so you can push without a dramatic monologue at the terminal.

SSH keys

SSH is the slick option. Generate a key pair on your machine and add the public key to GitHub. Once the key is installed pushing becomes friction free.

ssh-keygen -t ed25519 -C 'your_email@example.com'
# then copy the public key and add it to GitHub

HTTPS with a personal access token

If you prefer HTTPS create a personal access token in GitHub and use that instead of your account password. That avoids repeated prompts and is more secure than a plain password.

Dealing with conflicts without melodrama

Sometimes the remote has changes you do not. Fetch them and integrate before pushing again.

git fetch origin
git merge origin/main

Or if you prefer a cleaner history use rebase instead of merge. Resolve conflicts locally then push. This avoids surprise merge commits that look like emotional baggage.

Quick troubleshooting checklist

• Authentication failed Try SSH keys or use a personal access token for HTTPS
• Push rejected because branch is behind Fetch the remote and merge or rebase then push again
• Want easier pushes Use git push without -u once upstream is set

Final tips

Keep commits focused. Use branch names that make sense. Set up SSH keys if you like being efficient. If something breaks read the error message and then curse quietly. Repeat until push succeeds.

Now go push that code and pretend it was always meant to work this way.