From 2c77bd80598a359a51fc7e1ffa675034b9f6d5a8 Mon Sep 17 00:00:00 2001 From: "github-classroom[bot]" <66690702+github-classroom[bot]@users.noreply.github.com> Date: Tue, 7 May 2024 22:09:50 +0000 Subject: [PATCH 1/6] GitHub Classroom Feedback --- .github/.keep | 0 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 .github/.keep diff --git a/.github/.keep b/.github/.keep new file mode 100644 index 0000000..e69de29 From 495dc6640e7933cbce6861407391a2eebfdbb1b8 Mon Sep 17 00:00:00 2001 From: "github-classroom[bot]" <66690702+github-classroom[bot]@users.noreply.github.com> Date: Tue, 7 May 2024 22:09:50 +0000 Subject: [PATCH 2/6] Setting up GitHub Classroom Feedback From 93ad14027fefdf1bb99e2163d79055be3d9a3fc2 Mon Sep 17 00:00:00 2001 From: "github-classroom[bot]" <66690702+github-classroom[bot]@users.noreply.github.com> Date: Tue, 7 May 2024 22:09:53 +0000 Subject: [PATCH 3/6] add deadline --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 483845a..4f1ec31 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,4 @@ +[![Review Assignment Due Date](https://classroom.github.com/assets/deadline-readme-button-24ddc0f5d75046c5622901739e7c5dd533143b0c8e959d652212380cedb1ea36.svg)](https://classroom.github.com/a/JWsseB-r) # :wave: The Basics of GitHub ## 🤓 Course overview and learning outcomes From 525955633dd3888e0b710e4970be98af25135815 Mon Sep 17 00:00:00 2001 From: Janice Bailey <56306096+janiceb75@users.noreply.github.com> Date: Thu, 9 May 2024 07:57:31 -0400 Subject: [PATCH 4/6] Create LEARNING.md --- LEARNING.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 LEARNING.md diff --git a/LEARNING.md b/LEARNING.md new file mode 100644 index 0000000..38f1922 --- /dev/null +++ b/LEARNING.md @@ -0,0 +1,30 @@ + +# GITHUB LESSONS :school_satchel: + + + + +### Topics I feel comfortable with + +* Knowing the difference between Github and Git. + * Basically, they are both version control systems, but Github is a software program that + that has the open source Git, "under the hood", but offers a user interface for ease of use. + +* Cloning a repo + * This involves running a "git clone (followed by URL)" command to bring down a local copy of the repo. This brings down all the branches that exist in that repo + * Once this is done, I should create my own branch to keep my code changes seperate from the main code. I know I can do this via a "git checkout -b nameofmybranch" + +* Making Commits, pushing and pulling + * I currently use Github at work and have had to perform these actions a few times during pairing sessions. I am comfortable with what these commands are, but sometimes, may need to Google the exact command. I know that if I want to push the changes + that I made in my code to the main branch, I would push the code. Piror to doing that I would need to stage the file via a "git add ." and then add my comments via a "commit -m" + * If I want to make sure I have the latest updates on the remote branch I would perform a "git pull" + + + + + + + +### Topis I feel I need more clarity on + + * From 941c9379e93a075b70b43ea6f2695c39f8d0d2e7 Mon Sep 17 00:00:00 2001 From: Janice Bailey <56306096+janiceb75@users.noreply.github.com> Date: Sun, 12 May 2024 12:53:44 -0400 Subject: [PATCH 5/6] Update LEARNING.md --- LEARNING.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/LEARNING.md b/LEARNING.md index 38f1922..7d1b07a 100644 --- a/LEARNING.md +++ b/LEARNING.md @@ -14,7 +14,7 @@ * This involves running a "git clone (followed by URL)" command to bring down a local copy of the repo. This brings down all the branches that exist in that repo * Once this is done, I should create my own branch to keep my code changes seperate from the main code. I know I can do this via a "git checkout -b nameofmybranch" -* Making Commits, pushing and pulling +* Making Commits, pushing and pulling on a basic level * I currently use Github at work and have had to perform these actions a few times during pairing sessions. I am comfortable with what these commands are, but sometimes, may need to Google the exact command. I know that if I want to push the changes that I made in my code to the main branch, I would push the code. Piror to doing that I would need to stage the file via a "git add ." and then add my comments via a "commit -m" * If I want to make sure I have the latest updates on the remote branch I would perform a "git pull" @@ -25,6 +25,13 @@ -### Topis I feel I need more clarity on +### Topics I feel I need more clarity on - * + * The process of PRs (Pull Requests). I believe that initially I was getting the pull request confused with the regular git command line of "git pull". From going over the material and then remembering being walked through this (very quickly) during a pairing session at work, I realize I need more + clarity and experience doing this. There are so many different options with this such as pulling from forks (which is a new concept for me), as well + the base and rebase options. + + * I have not worked with Codebases yet and I believe I understand the idea of them, but I need some expeirence working with them eventually to feel + comfortable. + + From 2434fc0c9d282b6c27206adbdbdfbf4b1b7c2b04 Mon Sep 17 00:00:00 2001 From: Janice Bailey <56306096+janiceb75@users.noreply.github.com> Date: Sun, 12 May 2024 21:56:40 -0400 Subject: [PATCH 6/6] Update LEARNING.md --- LEARNING.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/LEARNING.md b/LEARNING.md index 7d1b07a..fc1414b 100644 --- a/LEARNING.md +++ b/LEARNING.md @@ -17,7 +17,8 @@ * Making Commits, pushing and pulling on a basic level * I currently use Github at work and have had to perform these actions a few times during pairing sessions. I am comfortable with what these commands are, but sometimes, may need to Google the exact command. I know that if I want to push the changes that I made in my code to the main branch, I would push the code. Piror to doing that I would need to stage the file via a "git add ." and then add my comments via a "commit -m" - * If I want to make sure I have the latest updates on the remote branch I would perform a "git pull" + * If I want to make sure I have the latest updates on the remote branch I would perform a "git pull" + * I need more clairity and work with forks as well.