From 1ce942fde72874edad8afda5755877c8e06076f7 Mon Sep 17 00:00:00 2001 From: Jared Siemen Date: Mon, 25 Jul 2022 16:39:41 -0400 Subject: [PATCH 1/2] Clone repo to local computer and answer first 8 questions --- answers.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/answers.txt b/answers.txt index 6b2a10f..76ae32a 100644 --- a/answers.txt +++ b/answers.txt @@ -1,3 +1,15 @@ Your answers go here! Please include your name and number your answers. ================================================== + +Name: Jared Siemen + +Answers: +1. Linus Torvalds +2. He is the main developer behind Linux. +3. Initially released in 2005. +4. git init +5. Git push takes the changes that you've saved and committed locally and sends them to your remote repository on Github. +6. A .gitignore file tells git which files and directories to ignore when staging and committing. This way you don't push sensitive information to the internet that shouldn't be out there, or to ignore large files. +7. A fork creates a copy of the repository that is completely independent of the original repo. You would want to do this to make changes to code without changing any of the code in the original repo. +8. A clone creates a local copy of the repository this is linked to the remote repo it was cloned from. You can then make changes and push the changes back up to that repo. You can have as many clones as you want. \ No newline at end of file From 835fc849305c215f8b901b61ddf198a32241e93d Mon Sep 17 00:00:00 2001 From: Jared Siemen Date: Mon, 25 Jul 2022 16:46:52 -0400 Subject: [PATCH 2/2] Finish answering questions --- answers.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/answers.txt b/answers.txt index 76ae32a..a59b4ec 100644 --- a/answers.txt +++ b/answers.txt @@ -12,4 +12,6 @@ Answers: 5. Git push takes the changes that you've saved and committed locally and sends them to your remote repository on Github. 6. A .gitignore file tells git which files and directories to ignore when staging and committing. This way you don't push sensitive information to the internet that shouldn't be out there, or to ignore large files. 7. A fork creates a copy of the repository that is completely independent of the original repo. You would want to do this to make changes to code without changing any of the code in the original repo. -8. A clone creates a local copy of the repository this is linked to the remote repo it was cloned from. You can then make changes and push the changes back up to that repo. You can have as many clones as you want. \ No newline at end of file +8. A clone creates a local copy of the repository this is linked to the remote repo it was cloned from. You can then make changes and push the changes back up to that repo. You can have as many clones as you want. +9. NEVER PUT A GITHUB REPO INSIDE ANOTHER REPO +10. True \ No newline at end of file