GitHub Code Commit Methods: A Complete Summary

🕐 2025-12-02 ✍️ Moyi Foreign Trade

1. Initial Setup

echo "# supereditor" >> README.md

git init #initialize the repository

git add README.md #add a single file; omitting the filename adds all files

git config --global user.name xxx #configure git

git commit -m "first commit" #commit the staged changes to the local repository with a message

git branch -M main #force-rename the current or specified branch to main

git remote add origin https://github.com/xxx/xxx.git #link the remote repository for the first time

git push -u origin main #push the code

2. How to Set Up a Proxy for GitHub

Global proxy settings

git config --global http.proxy http://127.0.0.1:1080

git config --global https.proxy https://127.0.0.1:1080

Proxy only GitHub

git config --global http.https://github.com.proxy https://127.0.0.1:1080

git config --global https.https://github.com.proxy https://127.0.0.1:1080

SOCKS5 proxy settings

git config --global http.https://github.com.proxy socks5://127.0.0.1:1086

git config --global https.https://github.com.proxy socks5://127.0.0.1:1086

Unset the proxy

git config --global --unset http.https://github.com.proxy

git config --global --unset http.https://github.com.proxy

View existing configuration

git config --global -l

GitHub Code Commit Methods: Pre-Check Checklist

Nothing is worse for tutorial-style content than copying commands while ignoring differences in your environment. Different system versions, web servers, plugin combinations and permission settings can all affect the final result. Before you start, record your current configuration and take a snapshot or backup if needed, so you can roll back quickly even if a step goes wrong.

Things to confirm before you start

System and software versions:Confirm the versions of Windows, Debian, Nginx, Apache, WordPress or related tools.
Permissions:When credentials, certificates or config files are involved, first confirm the current user has sufficient permissions.
Backups:Copy the original file before modifying any config file; for WordPress sites, back up the database too.
Testing method:Verify after each change instead of waiting until everything is done to troubleshoot.

Debugging approach

When an error occurs, first figure out which layer it happens in: browser, DNS, server, application, plugin or permissions. Breaking the problem into small pieces works better than repeatedly searching for the whole error message. For issues involving WordPress, Nginx, certificates or proxies, logs are usually more reliable than the front-end page.

If paths or menus in a tutorial don't match your environment, trust what your current system displays and locate the equivalent feature by keywords. Windows Control Panel, WordPress plugin menus and cloud console entry points in particular often move around between versions.

Ongoing maintenance tips

Fixing a problem once doesn't mean it's gone forever. Write down the key commands, the files you changed, when you changed them and the verification results. When you later migrate servers, upgrade plugins or switch themes, these notes will save you a lot of debugging time.