[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-573408-105":53,"doc-detail-573408-en":126},{"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":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","git-crash-course-version-control-basics-and-github-workflow","Git crash course - Version control basics and GitHub workflow","","A crash-course style introduction to version control with Git, explaining why teams and individuals use it to manage change history, track who modified what and when, and avoid losing work. Covers core local Git commands (init, status, add, commit, log, diff, branch, checkout, merge, stash) and clarifies how commits store snapshots. Extends to collaborative development using GitHub remotes, including pull requests, forking, cloning, remote setup, rebasing on pull, pushing, and updating main after merges.",{"@graph":63,"@context":118},[64,80,101],{"@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-crash-course-version-control-basics-and-github-workflow/573408/",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-crash-course-version-control-basics-and-github-workflow/573408.png","ImageObject",442,249,{"name":88,"@type":89},"Nguyễn Văn Học","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-18","2026-10-14",true,{"@type":98,"interactionType":99,"userInteractionCount":79},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"Why are version control systems used?","Question",{"text":108,"@type":109},"They record the history of changes over time, including who changed what, when, and why. They also help prevent losing work when alone and enable collaboration through merging and branching.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How do you use Git locally in the basic workflow?",{"text":113,"@type":109},"Initialize a repository, check status, add files to the staging area, commit changes, and then use log and diff to inspect history and differences. Branching, checkout, merge, and stash support different development paths and temporary changes.",{"name":115,"@type":106,"acceptedAnswer":116},"What is the proposed GitHub workflow for collaboration?",{"text":117,"@type":109},"Do not merge directly into the central remote. Create a branch, push it, then open a pull request so changes can be discussed and improved before merging; after approval and merge, update main and remove the local branch.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},573408,1792015514,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":79,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":8,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":139,"read_time":79},1374402739827,"https://ap-avatar.wpscdn.com/avatar/14000c97e7351f1a627?x-image-process=image/resize,m_fixed,w_180,h_180&k=1787885694763230660","Git crash course  \nThomas Breuer  \nLehrstuhl f􀁿ur Algebra und Zahlentheorie, RWTH Aachen University, Germany  \nSummer School, September 06, 2021  \nAim of this talk  \n􀀏 Version control systems: Why do we use them?  \n􀀏 How can we use the version control system git locally?  \n􀀏 How do we use git with the GitHub services, for the development of OSCAR (and for this summer school)?  \n􀀏 This is all very basic (but still looks complicated) .  \nVersion control systems { why?  \n􀀏 (for software development, writing papers, . . . )  \n􀀏 record the history of changes over time  \n􀀏 for each revision (timestamp): Who changed what , when, and why?  \n􀀏 when working alone:  \nno danger to lose parts of the work (due to the backups), undo changes  \n􀀏 when working with others:  \n\\merge\" contributions from di􀀋erent sides into one source  \n􀀏 \\branch\": maintain di􀀋erent versions of one software  \n􀀏 if public: admit contributions from outside  \nGit  \n  is a version control system,  \n  is free,  \n  does not need a central server (is \\decentralized\"), users' repositories have the full history information, the di􀀋erent repositories are equally good,  \n  has GUIs, but here we show just the command line version,  \n  calls the revisions/snapshots commits.  \nA live session with git  \n(commands in order of appearance)  \ngit init ,  \ngit status ,  \ngit add \u003C\u003Cfiles>> , git commit ,  \ngit log ,  \ngit diff ,  \ngit diff--cached ,  \ngit diff \u003C\u003Cold>> \u003C\u003Cnew>> ,  \ngit branch , git checkout \u003C\u003Cbranch>> , git merge \u003C\u003Cbranch>> ,  \ngit stash ,  \ngit stash pop.  \nGitHub: Use remote repositories  \nUp to now, we have used git on the local computer only.  \nFor collaborative work,  \nwe use also public remote repositories,  \nhosted [by GitHub.com](by GitHub.com) ([https://github.com](https://github.com) ) .  \n(There are alternatives; we use GitHub.)  \nThe services are free and open.  \nThe code is in git repositories.  \nWe use branching and merging (in principle . . . ) .  \nWe interact with GitHub via the command line and via a web interface.  \nProposed GitHub work􀀍ow  \nDo not directly merge your changes into the (central) remote repository.  \nCreate a so-called pull request from your branch, which then can be discussed, improved, discussed,   , and eventually merged.  \ncentral remote  \nfork  \n~~􀀛 ~~  \npull request  \nuser's remote  \n@ push   clone  \n6  \npull @ ?  \n@R  \nuser's local  \nProposed GitHub work􀀍ow: Setup  \n􀀏 Make sure that you have a GitHub account, and that local username and e-mail address 􀀌t to the values of the account. Check with git config-l ,  \nset with git config [user.name](user.name) \"...\" and  \ngit config [user.email](user.email) \"...\".  \n􀀏 Create/take a central remote repository. (Here: [https://github.com/oscar-system/Summerschool21Exercises.jl](https://github.com/oscar-system/Summerschool21Exercises.jl) )  \n􀀏 Create your own remote copy via fork.(Click the button in the web page of the repository.)  \n􀀏 Create your own local copy via clone.  \n(Copy the URL under Code/Clone in the web page,  \nthen execute git clone with this URL on your computer. )  \n􀀏 Notify the central remote repository. On your computer, call: git remote add upstream \u003C\u003Curl-central>> .  \n(Check with git remote-v. )  \nNow git pull-r upstream main should work.  \nProposed Github work􀀍ow: Repeat  \n􀀏 In your local repository,  \n􀀏 create a new branch (git checkout-b \u003C\u003Cname>>),  \n􀀏 edit some 􀀌les,  \n􀀏 stage the changed 􀀌les (git add),  \n􀀏 commit the changes (git commit),  \n􀀏 incorporate changes in the remote main branch  \nsince you started editing (git pull-r upstream main;  \n-r means \\rebase\": rewrite the history such that  \nthe remote changes come 􀀌rst and the local changes come on top),􀀏 commit the updated version,  \n􀀏 and then push the new version to origin (git push; git will propose additional parameters) .  \n􀀏 In the web page of the central remote repository, GitHub will propose to create a pull request.  \nCheck that these are the changes you want to propose;  \nif not then go to the previou","cbCaijiWj57rBZfV","https://ap.wps.com/l/cbCaijiWj57rBZfV","pdf",82175,"English","# Aim of this talk\n## Version control systems (why)\n## Git (what it is)\n# A live session with git\n## Commands in order of appearance\n# GitHub: Use remote repositories\n## Proposed GitHub workflow\n## Setup\n## Repeat","[{\"question\":\"Why are version control systems used?\",\"answer\":\"They record the history of changes over time, including who changed what, when, and why. They also help prevent losing work when alone and enable collaboration through merging and branching.\"},{\"question\":\"How do you use Git locally in the basic workflow?\",\"answer\":\"Initialize a repository, check status, add files to the staging area, commit changes, and then use log and diff to inspect history and differences. Branching, checkout, merge, and stash support different development paths and temporary changes.\"},{\"question\":\"What is the proposed GitHub workflow for collaboration?\",\"answer\":\"Do not merge directly into the central remote. Create a branch, push it, then open a pull request so changes can be discussed and improved before merging; after approval and merge, update main and remove the local branch.\"}]","Git crash course - Version control basics and GitHub workflow | PDF",1791939197]