Hands-on Git Tasks - Part #3 of 5 | Navigating Project Branches

This post is part of a 5-post series on using Git.

Hands-on Git Tasks - Part #1 of 5 | First Git Commit

Hands-on Git Taks - Part #2 of 5 | Checking Git Objects

Hands-on Git Tasks - Part #3 of 5 | Navigating Project Branches

Hands-on Git Tasks - Part #4 of 5 | Using Remote Repository

Hands-On Git Tasks - Part #5 of 5 | Merging

Follow these steps for an example of how to navigate the branches of your project in your AWS Cloud9 environment. (For steps to create your Cloud9 Environment, go here: https://medium.com/@lewislampkin/creating-an-integrated-developer-environment-ide-in-the-cloud-in-two-minutes-c96e33b2fa3e)

01. Check the log
git log
git log --oneline
Notice that the HEAD is currently pointing to the main branch.

02. List the files
ls

03. Move to the first commit using the checkout commad
git checkout [hash]
Note: can use the full hash, or the shorter version from the "git log --oneline" This shows us what the repository looked like during the first commit

04. check git log again
git log

05. List the files from first commit
ls

06. Move to the 'Main' branch using the checkout command
git checkout main

07. check the log
git log

08. List files in the 'Main' branch
ls

If you want to find me, you can catch me, Lewis Lampkin, III at LinkedIn: https://www.linkedin.com/in/lewislampkin

If you want to read my blog: https://www.lewislampkin.com

Comments

Post a Comment

Popular posts from this blog

"This site uses cookies from Google to deliver its services and analyze traffic. Your IP address and user-agent are shared with Google along with performance and security metrics to ensure quality of service, generate usage statistics, and to detect and address abuse."
Read more

Orphaned No More: Adopting AWS Lambda

Image
Background HumanGov is a Model Automated Multi-Tenant Architecture (MAMA) that is meant to be used by the 50 states for personnel tracking. Currently the architecture is fully automated on AWS. The architecture is not ready for go-live. All actions so far are for a proof-of-concept that is presented to the Chief Technical Officer (CTO) for review. During the weekly team meeting, Ko (User Experience Lead) reports that his team has performed thousands of tests against the infrastructure, with moves, adds, and changes, and is not finding any issues in the application user interface. Woo (Infrastructure Lead) reports that there are hundreds of 'orphaned' files in the S3 bucket. (These files are considered 'orphaned' because they do not have corresponding records in the DynamoDB table.) Kim (Tech Lead) reports that there is not a trigger to delete the file from the bucket when a user is deleted from the DynamoDB database. Brady (Lawyer) reports that not deleting t
Read more

Containing the Chaos! | A Three-Part Series Demonstrating the Usefulness of Containerization to HumanGov

Background HumanGov is a Model Automated Multi-Tenant Architecture (MAMA) that is meant to be used by the 50 states for personnel tracking. Currently the architecture requires Amazon Elastic Compute Cloud (EC2) instances that are maintained by the HumanGov systems administrators. The systems administrators handle all the patching, operations, etc. Due to states wanting their data separate from each other, each state gets a separate set of EC2 instances, which means that as the application scales from one state up to 50 states, the systems administrators will have to patch 50x as many EC2 instances. The system administrators report that they have begun to schedule more and more overtime to handle the maintenance windows for updating the EC2 instances. The lead developer remarked that it was taking longer and longer for new application deployments to get rolled out as the infrastructure grew and more states came on board. By the way, the development environment does not have standa
Read more