Pushing Code to Remote Repository with Git: How to Push Local Branches to GitHub/GitLab

The purpose of pushing code to a remote repository is to enable team collaboration, code backup, or hosting on remote platforms (such as GitHub/GitLab). The core processes and key points are as follows: **Preparation**: Ensure there are committed modifications in the local repository (`git add .` + `git commit -m "description"`), and the remote repository is already associated (default `origin`, established during cloning). **Push Commands**: - **First Push**: Specify the remote repository and branch using the syntax `git push [remote-repo-name] [local-branch-name]:[remote-branch-name]`, e.g., `git push -u origin dev` (`-u` automatically associates the branch for subsequent simplification). - **Subsequent Pushes**: If the branch is already associated, simply use `git push`. When branch names differ, use `git push origin local-branch:remote-branch` (e.g., `feature:new-feature`). **Verification and Troubleshooting**: After pushing, check the remote platform's webpage. Common issues: - Conflict: Resolve conflicts after `git pull` and then push again; - Permission: Verify account/repository permissions or re-enter credentials; - Accidental Push: If not yet pulled, use `--force` (note: use with caution).