Skip to content

ericsMoneyTeam (Group 1) - Jared Siemen #38

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
siemenjm wants to merge 2 commits into
base: master
Choose a base branch
from
Open

ericsMoneyTeam (Group 1) - Jared Siemen #38

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1ce942f
Clone repo to local computer and answer first 8 questions
siemenjm Jul 25, 2022
835fc84
Finish answering questions
siemenjm Jul 25, 2022
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
14 changes: 14 additions & 0 deletions answers.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,17 @@
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.
9. NEVER PUT A GITHUB REPO INSIDE ANOTHER REPO
10. True