Skip to content

Update README.md #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
CJDawson609 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update README.md #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 12 additions & 7 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ Make sure you have a GitHub account, and your [Personal Access Token has been se
```console
git --version
```
Record the output of the command as **`Answer 1`**.
Record the output of the command as **`git version 2.43.0`**.

4. Git needs to know your credentials (name and email). Issue the commands:

Expand All @@ -73,7 +73,8 @@ Make sure you have a GitHub account, and your [Personal Access Token has been se
git config --list
```

Record the output of this command as **`Answer 2`**.
Record the output of this command as **`user.email=cd648426@ohio.edu
user.name=Clarence Dawson`**.

5. Git includes a comprehensive help system. You can invoke help by issuing the following command

Expand All @@ -86,7 +87,7 @@ Make sure you have a GitHub account, and your [Personal Access Token has been se
git add --help
```

What happens when you type `git --help`? Record your answer as **`Answer 3`**.
What happens when you type `git --help`? Record your answer as **`Shows me possbile commands I can do`**.

---
**Creating and maintaining a repository**
Expand Down Expand Up @@ -135,15 +136,16 @@ Make sure you have a GitHub account, and your [Personal Access Token has been se

One of the common commands we use is to check the status of our repo is the `git status` command.

Type the status command inside the `git-lab` directory and record the output of this command as **`Answer 4`**.
Type the status command inside the `git-lab` directory and record the output of this command as **`README.md
answers.md`**.

You now have an untracked file in your working area. Let's track the file by staging it. Issue the command:

```console
git add README.md
```

Check the status of your project and record the output of the command as your answer to **`Answer 5`**.
Check the status of your project and record the output of the command as your answer to **`new file: README.md`**.

Did you notice the different file name colors in the two status command? Add the second file `answers.md` to the staging area.

Expand All @@ -157,7 +159,7 @@ Make sure you have a GitHub account, and your [Personal Access Token has been se

Messages in the commit command is very important. It describes what has happened since the last commit. It is specially helpful when working with teammates on the same project.

Issue the status command again and record your output as **`Answer 7`**.
Issue the status command again and record your output as **` answers.md`**.

The above workflow outlines the steps that you usually take to create a commit (snapshot) of your repository at any given time.

Expand All @@ -172,7 +174,10 @@ Make sure you have a GitHub account, and your [Personal Access Token has been se
* `HEAD->master`: a pointer to a repository called `master`. `master` is your main repository `branch` name. More on branching later.
* Author, email, date, and comment made while committing.

Record the output of the `git log` as **`Answer 8`**.
Record the output of the `git log` as **commit d7d7fa1f131519ed5d680fc25abf8cdf5f6cdfba (HEAD -> master)
Author: Clarence Dawson <cd648426@ohio.edu>
Date: Mon Feb 9 17:00:21 2026 -0500
`**.

---
**Working with remote repositories on GitHub**
Expand Down