task

learn GIT

day# 7

[REFERENCE]

1. ] # 2568 - overview git in technology-software/developer/source-code-managment
2. ] # 4076 - overview git in project-035/planning/documentation
3. ] # 4522 - create FAQ - about git - not really a FAq, more of a PAQ - Personally Asked
4. ] # ### - ignore this

[previously]

1. [2014-03-15] day# 1 - Git Started
1. ] download and install git, ] configure git, ] create an ART overview git ]
2. [2014-03-16] day# 2 - REVIEW VIDEO tutorial
1. ] review tutorial, ] start MY prj-001, ] a few questions, ] abondoned lrn-git project ???
3. [2014-12-07] day# 3 - RETURN to git, addED SCENARIO'S
1. x] COMPLETE interactive tutorial on github to practice using git Bash CLI and learn me some git commands
2. x] layed out some different use case scenario's for how 1 might be using git, see below ...
3. [2014-12-07] SCENE 1 - you are CREATE a new local project
4. [2014-12-07] SCENE 2 - you HAVE an existing local project
5. [2014-12-07] SCENE 3 - you HAVE/WANT to work on an existing remote project, (clone to local, make changes, push to remote)
6. [2014-12-07] SCENE 4 - GET(clone) an existing remote project for  inclusion into ...
4. [2014-12-08] day# 4 - create repo, add remote repo, push repo to remote,
1. +] SCENARIO - ADDing some component into your project
2. x] forwarded in /NEXT items from previous days (1-3)
5. [2014-12-08] day# 5 - create a branch, switch between branches, delete a branch
1. x] what is a branch, creating a branch, making changes to your code within the branch, switching back to a different branch and
6. [2014-12-14] day # 6 - merge, pull,
1. ] merge is when you combine branches into the master branch,

 

[currently]

1. [2014-12-09] SCENE 1 - CREATE a new local project(contd) - TAGging and LOGing
1. ] Tag - it's recommended to create tags for software releases. this is a known concept, which also exists in SVN.
2. ] Log - enables you to view all the documented changes that have been made to a repository,
2. ] git tag 1.0.0 1b2e1d63ff
1. ] to create a new tag named 1.0.0 for the commit identified by 1b2e1d63ff
2. ] the 1b2e1d63ff is the first 10 characters of the commit id you want to reference with your tag
3. ] to git the commit id, use
4. +] REF semantic version numbers - for informaton on using software version numbers
3. ] git log
1. ] you can study repository history
2. ] You can add a lot of parameters to make the log look like what you want.
4. ] EXAMPLE - git log entry
1. ] commit b652edfd888cd3d5e7fcb857d0dabc5a0fcb5e28
2. ] Author: Try Git try_git@github.com
3. ] Date:   Sat Oct 10 08:30:00 2020 -0500
4. ] Description: " feature 223 - hilight on change"
5. ] git log --author=bob
1. ] To see only the commits of a certain author:
6. ] git log --pretty=oneline
1. ] To see a very compressed log where each commit is one line
7. ] git log --graph --oneline --decorate --all
1. ] see an ASCII art tree of all the branches, decorated with the names of tags and branches
8. ] git log --name-status
1. ] See only which files have changed
2. ] These are just a few of the possible parameters you can use. For more, see
9. ] git log --help
1. ] git <command> --help
10. ] SUMMARY
1. ] use tag command to tag your commits with a version#
2. ] use log to view commit history,
3. ] use log options to view commit history in the format that you specify
4. ]

[next]

1. [2014-12-dd] day# 8 replace local changes
1. ] # # - undo changes to your local repo,
2. [2014-12-08] NEW
1. ] now what - we have our local repo, we have pushed our local repo to a remote server, anyone can clone it
2. ] changes -  edit file, git add, git commit,
3. ]

Details

ID: 4540

NAME: day-7-learn-git

DESCRIPTION: NEXT STEPS ] tagging ] logging

START DATE TIME: 2014-12-10 21:59:01

EST DURATION: 01:00:00

END DATE TIME: 2014-12-10 22:59:01

STATUS: Completed

PRIORITY: -5

OWNER ID: 75

photos

actions

Agenda Email task SMS task Priorities