git push transfers committed local changes to a remote repository. Use it after git add and git commit, once the local repository knows where the remote is. section 2.3.6 section 2.4.3
A practical push workflow is:
- Enter the project directory, initialize Git if necessary, create a .gitignore, stage files, and commit the changes. section 2.3.4
- Create the remote repository, then connect it locally with git remote add origin <repository-url>. section 2.4 section 2.4.3
- Push the committed branch with git push origin main. section 2.4.3
- For a separately hosted virtual-machine repository, configure a remote such as vm and run git push vm main. section 3.3.3
Pushing a project to GitHub
From the project directory, run git remote add origin https://github.com/yourusername/roadtok8s-py.git, then run git push origin main. Repeat the process for the other application. section 2.4.3
Pushing to a VM remote
Configure ssh://root@45.79.47.168/var/repos/roadtok8s/py.git as vm, then run git push vm main. The vm name distinguishes this special remote from the conventional origin remote. section 3.3.3
Diagnose failures by checking configured remotes with git remote -v and the current branch with git branch --show-current. Permission errors indicate remote access problems; a missing main refspec indicates a branch-name mismatch. After deleting Git history, git push origin main --force may overwrite remote changes and requires caution. section 2.4.3 section 3.3.3
