edit-task
Home
Up
Delete
Task Name:
Task Description:
NEXT STEPS ] tagging ] logging
TaskGroup ID:
Start Date:
Start Time:
Duration:
Priority:
Status:
To Do
Completed
In Process
Add Photo:
Owner ID:
Content:
use HTML
Edit Content
<h1 style="text-align: center;">learn GIT</h1> <h2 style="text-align: center;">day# 7</h2> <h2><strong>[REFERENCE] </strong></h2> <ol> <li>] # 2568 - <a href="/view/article?id=2568" target="_blank">overview git</a> in technology-software/developer/source-code-managment</li> <li>] # 4076 - <a href="/view/article?id=4076" target="_blank">overview git</a> in project-035/planning/documentation</li> <li>] # 4522 - <a href="/view/task?id=4522" target="_blank">create FAQ</a> - about git - not really a FAq, more of a PAQ - Personally Asked</li> <li>] <span style="background-color: #888888;"># ###</span> - ignore this</li> </ol> <h2>[previously]</h2> <ol> <li><strong>[2014-03-15] <a href="/view/task?id=3663" target="_blank">day# 1 - Git Started</a></strong></li> <ol> <li>] download and install git, ] configure git, ] create an ART overview git ]</li> </ol> <li><strong>[2014-03-16] <a href="/view/task?id=3672" target="_blank">day# 2 - REVIEW VIDEO tutorial</a></strong></li> <ol> <li>] review tutorial, ] start MY prj-001, ] a few questions, ] abondoned lrn-git project ???</li> </ol> <li><strong>[2014-12-07] <a href="/view/task?id=4477" target="_blank">day# 3 - RETURN to git, addED SCENARIO'S</a></strong></li> <ol> <li>x] COMPLETE <span style="text-decoration: underline;">interactive tutorial</span> on github to practice using git Bash CLI and learn me some git commands</li> <li>x] layed out some different use case scenario's for how 1 might be using git, see below ...</li> <li><span style="background-color: #ffff99;"><strong>[2014-12-07] SCENE 1 - you are CREATE a new local project </strong></span></li> <li><span style="background-color: #ffff99;"><strong>[2014-12-07] SCENE 2 - you HAVE an existing local project </strong></span></li> <li><span style="background-color: #ffff99;"><strong>[2014-12-07] SCENE</strong><strong> 3 - you HAVE/WANT to work on an existing remote project, (clone to local, make changes, push to remote)</strong></span></li> <li><span style="background-color: #ffff99;"><strong>[2014-12-07] SCENE</strong><strong> 4 - GET(clone) an existing remote project for inclusion into ...</strong></span></li> </ol> <li><strong>[2014-12-08] <a href="/view/task?id=3713" target="_blank">day# 4</a> - create repo, add remote repo, push repo to remote, </strong></li> <ol> <li>+] SCENARIO - ADDing some component into your project</li> <li>x] forwarded in /NEXT items from previous days (1-3)</li> </ol> <li><strong>[2014-12-08] </strong><a href="/view/task?id=4519" target="_blank"><strong>day# 5</strong></a><strong> - create a branch, switch between branches, delete a branch</strong></li> <ol> <li>x] what is a branch, creating a branch, making changes to your code within the branch, switching back to a different branch and</li> </ol> <li><strong>[2014-12-14] <a href="/view/task?id=4524" target="_blank">day # 6</a> - merge, pull, </strong></li> <ol> <li>] merge is when you combine branches into the master branch,</li> </ol></ol> <p> </p> <h2>[currently]</h2> <ol> <li><strong><span style="background-color: #ffff99;">[2014-12-09] SCENE 1 - CREATE a new local project(contd)</span> - TAGging and LOGing</strong></li> <ol> <li>] <strong>Tag -</strong> it's recommended to create tags for software releases. this is a known concept, which also exists in SVN.</li> <li><strong>] Log </strong>- enables you to view all the documented changes that have been made to a repository,</li> </ol> <li><strong>] git tag 1.0.0 1b2e1d63ff</strong></li> <ol> <li>] to create a new tag named 1.0.0 for the commit identified by 1b2e1d63ff</li> <li>] the 1b2e1d63ff is the first 10 characters of the commit id you want to reference with your tag</li> <li>] to git the commit id, use</li> <li>+] REF semantic version numbers - for informaton on using software version numbers</li> </ol> <li><strong>] git log</strong></li> <ol> <li>] you can study repository history</li> <li>] You can add a lot of parameters to make the log look like what you want.</li> </ol> <li><strong>] EXAMPLE - git log entry</strong></li> <ol> <li>] commit b652edfd888cd3d5e7fcb857d0dabc5a0fcb5e28</li> <li>] Author: Try Git try_git@github.com</li> <li>] Date: Sat Oct 10 08:30:00 2020 -0500</li> <li>] Description: " feature 223 - hilight on change"</li> </ol> <li><strong>] git log --author=bob</strong></li> <ol> <li>] To see only the commits of a certain author:</li> </ol> <li><strong>] git log --pretty=oneline</strong></li> <ol> <li>] To see a very compressed log where each commit is one line</li> </ol> <li><strong>] git log --graph --oneline --decorate --all</strong></li> <ol> <li>] see an ASCII art tree of all the branches, decorated with the names of tags and branches</li> </ol> <li><strong>] git log --name-status</strong></li> <ol> <li>] See only which files have changed</li> <li>] These are just a few of the possible parameters you can use. For more, see</li> </ol> <li><span style="background-color: #00ff00;"><strong>] git log --help</strong></span></li> <ol> <li><span style="background-color: #00ff00;">] git <command> --help</span></li> </ol> <li><strong>] SUMMARY</strong></li> <ol> <li>] use tag command to tag your commits with a version#</li> <li>] use log to view commit history,</li> <li>] use log options to view commit history in the format that you specify</li> <li>]</li> </ol></ol> <h2>[next]</h2> <ol> <li><strong>[2014-12-dd] day# 8 replace local changes</strong></li> <ol> <li>] # # - undo changes to your local repo,</li> </ol> <li><strong>[2014-12-08] NEW</strong></li> <ol> <li><strong>] now what - </strong>we have our local repo, we have pushed our local repo to a remote server, anyone can clone it</li> <li><strong>] changes - </strong>edit file, git add, git commit,</li> <li><strong>] </strong></li> </ol></ol>