Q. Demonstrate how you can implement the following tasks using Git CMD ; 1.Create a folder, name it TRACKCHANGES 2.Make the folder TRACKCHANGES readable to your VCS 3.Configure the username set to TRACKCHANGES 4.Configure the user email set to TRACKCHANGES 5.Configure automatic command line colouring for Git for easy reviewing 6.Check the status of TRACKCHANGES 7.Create a word document, name it MODIFICATIONSTRACKED 8.Check the status of TRACKCHANGES 9.Stage the file MODIFICATIONSTRACKED 10.Open the file MODIFICATIONSTRACKED, and then type "First set of changes" 11.Show the difference of what was staged but not yet committed 12.Perform a commit with a descriptive message 13.Show the commit history for the currently active branch 14.Create a new branch name it SECONDSETCHANGESBRANCH 15.Display a list of all branches available 16.Move to the branch SECONDSETCHANGESBRANCH 17.Open the file MODIFICATIONSTRACKED, and then type "Second set of changes" 18.Check the status of TRACKCHANGES 19.Show the difference of what was staged but not yet committed 20.Perform a commit with a descriptive message 21.Merge the branch master to SECONDSETCHANGESBRANCH 22.Checkout to the branch master 23.Open the file MODIFICATIONSTRACKED, and then type "Third set of changes" 24.Show the commits on master that are not on SECONDSETCHANGESBRANCH 25.Show the commits that changed the file, even across renames 26.Show the diff of what is in SECONDSETCHANGESBRANCH that is not in master 27.Apply any commits of current branch ahead of SECONDSETCHANGESBRANCH branch 28.Clear the staging area, rewrite the working tree from the second commit of branch master 29.Save the modified and staged changes 30.List the stack order of the stashed file changes
Q. Demonstrate how you can implement the following tasks using Git CMD ;
1.Create a folder, name it TRACKCHANGES
2.Make the folder TRACKCHANGES readable to your VCS
3.Configure the username set to TRACKCHANGES
4.Configure the user email set to TRACKCHANGES
5.Configure automatic command line colouring for Git for easy reviewing
6.Check the status of TRACKCHANGES
7.Create a word document, name it MODIFICATIONSTRACKED
8.Check the status of TRACKCHANGES
9.Stage the file MODIFICATIONSTRACKED
10.Open the file MODIFICATIONSTRACKED, and then type "First set of changes"
11.Show the difference of what was staged but not yet committed
12.Perform a commit with a descriptive message
13.Show the commit history for the currently active branch
14.Create a new branch name it SECONDSETCHANGESBRANCH
15.Display a list of all branches available
16.Move to the branch SECONDSETCHANGESBRANCH
17.Open the file MODIFICATIONSTRACKED, and then type "Second set of changes"
18.Check the status of TRACKCHANGES
19.Show the difference of what was staged but not yet committed
20.Perform a commit with a descriptive message
21.Merge the branch master to SECONDSETCHANGESBRANCH
22.Checkout to the branch master
23.Open the file MODIFICATIONSTRACKED, and then type "Third set of changes"
24.Show the commits on master that are not on SECONDSETCHANGESBRANCH
25.Show the commits that changed the file, even across renames
26.Show the diff of what is in SECONDSETCHANGESBRANCH that is not in master
27.Apply any commits of current branch ahead of SECONDSETCHANGESBRANCH branch
28.Clear the staging area, rewrite the working tree from the second commit of branch master
29.Save the modified and staged changes
30.List the stack order of the stashed file changes
Step by step
Solved in 3 steps
