[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-571428-105":53,"doc-detail-571428-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","git-cheat-sheet-version-control-with-git-made-easy","GIT CHEAT SHEET - Version control with Git-made easy","","Git commands and workflows presented as a cheat sheet, covering creating and cloning repositories, checking local changes, staging and committing, reviewing history, and using branches and tags. It also explains remote management operations such as fetch, pull, push, and deleting remote branches, plus merge and rebase with conflict handling and undo actions. Includes best practices: commit granularity, commit frequency, avoid half-done work, test before pushing, write clear commit messages, and use branches while treating version control as history management, not backups.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/git-cheat-sheet-version-control-with-git-made-easy/571428/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/git-cheat-sheet-version-control-with-git-made-easy/571428.png","ImageObject",442,249,{"name":88,"@type":89},"วิน","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-22","2026-10-13",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",7,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"How do you create a new Git repository and start version control?","Question",{"text":109,"@type":110},"Use git init to create a new local repository, or git clone to clone an existing remote repository into a new local copy.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What commands help you review local modifications and commit them?",{"text":114,"@type":110},"Use git status to see changed files and git diff to inspect differences. Stage with git add (including git add -p for partial staging), then commit with git commit or git commit -a.",{"name":116,"@type":107,"acceptedAnswer":117},"Which best practices should you follow to keep commits clean and safe?",{"text":118,"@type":110},"Commit related changes together, commit often but only complete work, test code before pushing, and write clear commit messages with a short summary and detailed body. Avoid using version control as a backup system and use branches to separate development lines.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},571428,1792014839,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":73,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":9},2336475104736,"https://ap-avatar.wpscdn.com/avatar/22000c4c5e0e5b17e70?x-image-process=image/resize,m_fixed,w_180,h_180&k=1786591360781797222","fournova  \nGIT CHEAT SHEET  \npresented by TOWER › Version control with Git-made easy  \nCREATE  \nClone an existing repository  \n $ git clone [ssh://user@domain.com/repo.git](ssh://user@domain.com/repo.git)[ ](ssh://user@domain.com/repo.git)Create a new local repository  \n$ git init  \nLOCAL CHANGES  \nChanged files in your working directory  \n$ git status  \nChanges to tracked files  \n$ git diff  \nAdd all current changes to the next commit  \n$ git add .  \nAdd some changes in \u003Cfile> to the next commit  \n$ git add -p \u003Cfile>  \nCommit all local changes in tracked files  \n$ git commit -a  \nCommit previously staged changes  \n$ git commit  \nChange the last commit  \nDon‘t amend published commits!  \n$ git commit --amend  \nCOMMIT HISTORY  \nShow all commits, starting with newest  \n$ git log  \nShow changes over time for a specific file  \n$ git log -p \u003Cfile>  \nWho changed what and when in \u003Cfile>  \n$ git blame \u003Cfile>  \nBRANCHES & TAGS  \nList all existing branches  \n$ git branch -av  \nSwitch HEAD branch  \n$ git checkout \u003Cbranch>  \nCreate a new branch based on your current HEAD  \n$ git branch \u003Cnew-branch>  \nCreate a new tracking branch based on a remote branch  \n $ git checkout --track \u003Cremote/bran- ch>  \nDelete a local branch  \n$ git branch -d \u003Cbranch>  \nMark the current commit with a tag  \n$ git tag \u003Ctag-name>  \nUPDATE & PUBLISH  \nList all currently configured remotes  \n$ git remote -v  \nShow information about a remote  \n$ git remote show \u003Cremote>  \nAdd new remote repository, named \u003Cremote>  $ git remote add \u003Cshortname> \u003Curl>  Download all changes from \u003Cremote>, but don‘t integrate into HEAD  \n$ git fetch \u003Cremote>  \nDownload changes and directly merge/integrate into HEAD  \n$ git pull \u003Cremote> \u003Cbranch>  \nPublish local changes on a remote  \n$ git push \u003Cremote> \u003Cbranch>  \nDelete a branch on the remote  \n$ git branch -dr \u003Cremote/branch>  \nPublish your tags  \n$ git push --tags  \nMERGE & REBASE  \nMerge \u003Cbranch> into your current HEAD  \n$ git merge \u003Cbranch>  \nRebase your current HEAD onto \u003Cbranch> Don‘t rebase published commits!  \n$ git rebase \u003Cbranch>  \nAbort a rebase  \n$ git rebase --abort  \nContinue a rebase after resolving conflicts  \n$ git rebase - -continue  \nUse your configured merge tool to solve conflicts  \n$ git mergetool  \nUse your editor to manually solve conflictsand (after resolving) mark file as resolved  \n$ git add \u003Cresolved-file>$ git rm \u003Cresolved-file>  \nUNDO  \nDiscard all local changes in your working directory  \n$ git reset --hard HEAD  \nDiscard local changes in a specific file  \n$ git checkout HEAD \u003Cfile>  \nRevert a commit (by producing a new commit with contrary changes)  \n$ git revert \u003Ccommit>  \nReset your HEAD pointer to a previous commit …and discard all changes since then  \n$ git reset --hard \u003Ccommit>  \n…and preserve all changes as unstaged changes  \n$ git reset \u003Ccommit>  \n…and preserve uncommitted local changes  \n$ git reset --keep \u003Ccommit>  \n30-day free trial available at [www.git-tower.com](www.git-tower.com)  \nVersion control with Git -made easy  \n fournova  \nVERSION CONTROL  \nBEST PRACTICES  \nCOMMIT RELATED CHANGES  \nA commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong.  \nWith tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.  \nCOMMIT OFTEN  \nCommitting often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having few large commits and sharing them rarely, in contrast, makes it hard to solve conflicts.  \nDON‘T COMMIT HALF-DONE WORK  \nYou should only commit code when it‘s completed. This doesn‘t mean you have to complete a whole, large feature before committing. Qu","cbCaim4Hqy2R56l8","https://ap.wps.com/l/cbCaim4Hqy2R56l8","pdf",259772,"English","# Create\n## Clone an existing repository\n## Create a new local repository\n# Local Changes\n## Check status and differences\n## Stage and commit changes\n# Commit History\n## View commits, diffs, and blame\n# Branches & Tags\n## Branch management and tags\n# Update & Publish\n## Remotes, fetch, pull, push\n# Merge & Rebase\n## Merge workflows and rebasing\n# Undo\n## Discard, revert, and reset\n# Version Control Best Practices\n## Commit related changes and commit often\n## Don’t commit half-done work\n## Test code before you commit\n## Write good commit messages\n## Version control is not a backup system\n## Use branches","[{\"question\":\"How do you create a new Git repository and start version control?\",\"answer\":\"Use git init to create a new local repository, or git clone to clone an existing remote repository into a new local copy.\"},{\"question\":\"What commands help you review local modifications and commit them?\",\"answer\":\"Use git status to see changed files and git diff to inspect differences. Stage with git add (including git add -p for partial staging), then commit with git commit or git commit -a.\"},{\"question\":\"Which best practices should you follow to keep commits clean and safe?\",\"answer\":\"Commit related changes together, commit often but only complete work, test code before pushing, and write clear commit messages with a short summary and detailed body. Avoid using version control as a backup system and use branches to separate development lines.\"}]","GIT CHEAT SHEET - Version control with Git-made easy | PDF",1791916943]