{"id":1225,"date":"2025-12-02T18:56:03","date_gmt":"2025-12-02T10:56:03","guid":{"rendered":"https:\/\/virtualcardx.com\/?p=1225"},"modified":"2026-07-07T00:30:05","modified_gmt":"2026-07-06T16:30:05","slug":"github-commit-code-commands-summary","status":"publish","type":"post","link":"https:\/\/virtualcardx.com\/en\/2025\/12\/02\/github-commit-code-commands-summary\/","title":{"rendered":"Summary of Github code submission methods"},"content":{"rendered":"
\"\"<\/figure>\n

\n

1. Initial operations<\/h2>\n
echo \"# supereditor\" >> README.md\n\ngit init # initialize repository\n\ngit add README.md # add single file Omitting the filename at the end is adding all files\n\ngit config --global user.name xxx # configure git\n\ngit commit -m \"first commit\" # commits changes from the staging area to the local repository with a commit note\n\ngit branch -M main # Forces the current branch or a specified branch to be renamed to main.\n\ngit remote add origin https:\/\/github.com\/xxx\/xxx.git # associates the remote repository for the first time\n\ngit push -u origin main # push code<\/code><\/pre>\n
2. How to set up proxy access to Github<\/h2>\n
Global Proxy Settings<\/h4>\n
git config --global http.proxy http:\/\/127.0.0.1:1080\n\ngit config --global https.proxy https:\/\/127.0.0.1:1080<\/code><\/pre>\n
Proxying GitHub only<\/h4>\n
git config --global http.https:\/\/github.com.proxy https:\/\/127.0.0.1:1080\n\ngit config --global https.https:\/\/github.com.proxy https:\/\/127.0.0.1:1080<\/code><\/pre>\n
sock5 proxy settings<\/h4>\n
git config --global http.https:\/\/github.com.proxy socks5:\/\/127.0.0.1:1086\n\ngit config --global https.https:\/\/github.com.proxy socks5:\/\/127.0.0.1:1086<\/code><\/pre>\n
Unproxy<\/h4>\n
git config --global --unset http.https:\/\/github.com.proxy\n\ngit config --global --unset http.https:\/\/github.com.proxy<\/code><\/pre>\n
Viewing existing configurations<\/h4>\n
git config --global -l<\/code><\/pre>\n
\n
\n
Summary of How to Push Code to GitHub: A Checklist Before You Begin<\/h2>\n
When creating technical tutorials, the biggest pitfall is copying commands verbatim while ignoring differences in the environment. Different system versions, web servers, plugin combinations, and permission settings can all affect the final outcome. Before proceeding, it\u2019s recommended that you document your current configuration and, if necessary, create a snapshot or backup. That way, even if you make a mistake during the process, you can quickly roll back the changes.<\/p>\n
We recommend confirming the following before proceeding<\/h3>\n