(public).sospep.subjects ~ view article ~ 001-git-going-scenarios

<h1 style="text-align: center;">git going - scenarios</h1>
<h2>[WHAT]</h2>
<ol>
<li>] by Don Sagrott, founder @sospep.com - this article outlines some common use case scenarios for working with git SCM software and remote code hosting repo's like github.com</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li>]&nbsp;</li>
</ol>
<h2>[WHERE]</h2>
<ol>
<li><strong>] READ THE FULL ARTICLE</strong></li>
<ol>
<li>] see the EXAMPLE section below</li>
</ol></ol>
<h2>[WHEN]</h2>
<ol>
<li>] 2017-05-01</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li><span style="background-color: #ffff99;"><strong>[SCENARIO-001] CREATE a new repo on your local machine, then PUSH it to your own hosted REMOTE repo&nbsp;</strong></span></li>
<ol>
<li><strong>[00:00] EXAMPLE OUTLINE PROCESS = # steps, ]&nbsp;</strong></li>
<ol>
<li>] using bash, navigate to the directory where you wish to copy the files into</li>
<li>] git init,&nbsp;</li>
<li>] git add,</li>
<li>] git commit</li>
<li>] git push ( from local to your remote repo)</li>
<li>] git pull ( from remote repo to your local machine)</li>
</ol>
<li><strong>[EXAMPLE =]&nbsp;</strong></li>
<ol>
<li>] sospep/guide&nbsp;</li>
</ol></ol>
<li><span style="background-color: #ffff99;"><strong><strong>[SCENARIO-002</strong>] CLONE an existing repo to your local machine, then PUSH your UPDATES back to the orig repo</strong></span></li>
<ol>
<li><strong>[00:00] EXAMPLE OUTLINE PROCESS = # steps, ]&nbsp;</strong></li>
<ol>
<li>] using bash, navigate to the directory where you wish to copy the files into</li>
<li>] git clone {path}&nbsp;</li>
<li>] EDIT source&nbsp;</li>
</ol>
<li><strong>[00:00] NEW task</strong></li>
<ol>
<li>x] launch bash and navigate to the directory where you want the repo to exist on your local machine</li>
<li><span style="background-color: #00ff00;">x] &gt; sh.exe --login</span></li>
</ol>
<li><strong>[00:00] NEW task</strong></li>
<ol>
<li>] ENTER the following command in bash, where {path} is the URL generated by the 'clone' button in github</li>
<li><span style="background-color: #00ff00;">] git clone {URL-cool-git-project}</span></li>
<li>] git clone http://github.com/tastejs/todoMVC.git</li>
</ol>
<li><strong>[00:00</strong><strong>] NEW task EDIT SOURCE</strong></li>
<ol>
<li>] EDIT-SOURCE - see EDIT process</li>
</ol>
<li><strong>[00:00] NEW task</strong></li>
<ol>
<li>] push changes back to the main repo || submit pull request</li>
</ol>
<li><strong>[EXAMPLE=]</strong></li>
<ol>
<li>]&nbsp;</li>
</ol>
<li><strong>[REFERENCE]</strong></li>
<ol>
<li>] http://stackoverflow.com/questions/651038/how-do-you-clone-a-git-repository-into-a-specific-folder</li>
</ol></ol>
<li><span style="background-color: #ffff99;"><strong><strong>[SCENARIO-003</strong>] FORK an existing repo</strong></span></li>
<ol>
<li>*] this make a copy of the repo you want on your github account</li>
<li>x] ?download? to your local machine USING ___</li>
<li>x] edit source - git add, git commit,&nbsp;</li>
<li><strong>[EXAMPLE=]</strong></li>
<ol>
<li>x] sospep/what-happens-when</li>
</ol>
<li><strong>[REFERENCE=]</strong></li>
<ol>
<li>]&nbsp;</li>
</ol></ol>
<li><span style="background-color: #ffff99;"><strong>[SCENARIO-004] CLONE an existing remote repo to your local machine, then PUSH it back to your own REMOTE repo</strong></span></li>
<ol>
<li><strong>[00:00] WHAT =&nbsp;</strong></li>
<ol>
<li>] clone a remote repo to your local machine, then PUSH it back(aka CREATE) your own REMOTE repo with some of the original projects contents</li>
<li>] EASIER = ] fork project @remote host ] clone fork (to localMachine), { ] EDIT source local }, ] push myfork, { ] submit pull request orig project }&nbsp;</li>
</ol>
<li><strong>[00:00] EXAMPLE OUTLINE PROCESS = 6 steps, ] local repo, ] clone remote repo, ] remote add, ] remote set-url, ] create repo on your ..., ] git push&nbsp;</strong></li>
<ol>
<li>*] using bash navigate to the local directory where you want the cloned app to live</li>
<li>x] git clone {url}</li>
<li>x] git remote add {name} {url}</li>
<li>x] git remote set-url origin {URL-remote-repo}</li>
<li>x] USE github.com UI to manually create repository &nbsp;</li>
<li>x] git push {name} {branch} || git push -u origin master</li>
</ol>
<li><strong>[00:00] NEW procedure IN prj-035-git-started/using-git/</strong></li>
<ol>
<li>x] # 452 - <a href="/view/step?id=452" target="_blank">LIST-steps</a>&nbsp;- detailed step by step process for cloning a remote repository to your local machine</li>
</ol></ol>
<li><span style="background-color: #cc99ff;"><strong>] EDIT source&nbsp;</strong></span></li>
<ol>
<li><strong>] EXAMPLE</strong></li>
<li>x] use VScode editor to change "index.html" ( triplicate line about "we now have 64 applications"&nbsp;</li>
<li>x] git add -A ( all changes)</li>
<li>x] git commit -a ( use "am" to get a different editor than vi to enter your commit msg)</li>
<li>] push changes back to a different repo</li>
</ol></ol>
<h2>[HOW-TO]</h2>
<ol>
<li><strong>[00:00] NEW task&nbsp;</strong></li>
<ol>
<li>*] SUCCESS - your project should be live on github, ready for any changes you make locally,</li>
<li>] you can take your git SKILLS to the next level, but its entirely up to you wether to ADVANCE or not, typically if you plan to have multiple contributors to your source base, you will</li>
</ol>
<li>
<div><strong>[00:00] NEW task IN&nbsp;</strong></div>
</li>
<ol>
<li><strong>] clone - any exisiting repository into your local machine</strong></li>
<li>] navigate to directory where you wish to copy the files into</li>
<li>] ENTER the following command in bash, where {path} is the URL generated by the 'clone' button in github</li>
<li>] git clone {path} .</li>
</ol>
<li>]&nbsp;</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>x] # 7282 -&nbsp;<a href="/view/task?id=7282" target="_blank">CREATE-article# 5729</a>&nbsp;-&nbsp;</li>
</ol>
<h2>[RELATED]</h2>
<div><ol>
<li>] BOOK -&nbsp;<a href="/view/chapters?id=263" target="_blank">git-started</a> - <a href="/view/article?id=2459" target="_blank">contents</a>&nbsp;</li>
</ol></div>
<h1 style="text-align: center;">&nbsp;</h1>

~ view article ~ Chapter] ch-005-git-going FROM [ Book] book-git IN [ libraries] prj-035-git-started