Advance Git and GitHub (Part II)

Advance Git and GitHub (Part II)

Day 10 #90daysofdevopschallange

Here we can start with tasks ... I am using Ec2 AWS here

Task 1:

Add a text file called version01.txt inside the Devops/Git/ with “This is first feature of our application” written inside.

This should be in a branch coming from master, [hint try git checkout -b dev], switch to dev branch ( Make sure your commit message will reflect as "Added new feature"). [Hint use your knowledge of creating branches and Git commit command]

  • version01.txt should reflect at the local repo first followed by the Remote repo for review. [Hint use your knowledge of Git push and git pull commands here]

Add a new commit in dev branch after adding the below-mentioned content in Devops/Git/version01.txt: While writing the file make sure you write these lines

  • 1st line>> This is the bug fix in a development branch

  • Commit this with the message “ Added feature2 in development branch”

  • 2nd line>> This is gadbad code

  • Commit this with the message “ Added feature3 in a development branch

  • 3rd line>> This feature will gadbad everything from now.

  • Commit with the message “ Added feature4 in the development branch

Restore the file to a previous version where the content should be “This is the bug fix in the development branch”

Task2 :

  • Demonstrate the concept of branches with 2 or more branches with a screenshot.

  • add some changes to dev the branch and merge that branch in master

  • as a practice try git rebase too, and see what difference you get.

Git merge :

Git Rebase: as a practice try git rebase too, and see what difference you get.

Task3:

  • Create a new branch and make some changes to it.

  • Use git stash to save the changes without committing them.

  • Switch to a different branch, make some changes and commit them.

  • Created 3 branches

git stash:

Switching to different branch,to make some changes

git log --online

Use git stash pop to bring the changes back and apply them on top of the new commits: moved back to the previous branch where we left the changes.

Task4:

  • In version01.txt of the development branch add below lines after “This is the bug fix in the development branch” that you added in Day10 and reverted to this commit.

  • Line2>> After bug fixing, this is the new feature with minor alterations”

    Commit this with the message “ Added feature2.1 in development branch”

  • Line3>> This is the advancement of the previous feature

    Commit this with the message “ Added feature2.2 in development branch”

  • Line4>> Feature 2 is completed and ready for release

    Commit this with the message “ Feature2 completed”

  • All these commits messages should be reflected in the Production branch too which will come out from the Master branch (Hint: try rebase).

Task5:

  • In the Production branch Cherry pick Commit “Added feature2.2 in development branch” and added the below lines in it:

  • The line to be added after Line3>> This is the advancement of the previous feature

  • Line 4>>Added a few more changes to make it more optimized.

  • Commit: Optimized the feature

Thanks for reading...

Happy Learning !!