Skip to content

hashDanChibueze - Homework Submission #102

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

hashDanChibueze - Homework Submission #102

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2d48ee0
MADE CHANGE TO README
discrete-void Jun 14, 2018
625795e
Second change made to the Readme markdown
discrete-void Jun 14, 2018
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
22 changes: 11 additions & 11 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,17 +1,17 @@
# Pre Course Git Fu
[Pre Class Video](https://youtu.be/ZihgMcrHOF4)

## Terms for learning Git
* Repository -
* Git - Version Control -
* Clone -
* Fork -
* History -
* Staging -
* Remote -
* Commit -
* Push -
* Repository - A repository in my own words can be seen as a storage for folders and different types of files that facilitate a project
* Git - Version Control - The Git version control
* Clone - A clone refers to a copy of a file in a git repository
* Fork - A fork refers to the copy of a repository
* History - A history refers to a record of acitivities in a git repo
* Staging - Staging refers to the situation where information about your next commit is recorded
* Remote - Remote refers to the location where the respective files are stored other than the local storage
* Commit - A commit can be seen as a command that records changes made in the repo to git
* Push - A push command simply updates the repository with respect to changes made by the commits

## Steps to our Lamba School Git Flow
## Steps to our Lambda School Git Flow
1. Fork repository
2. `git clone` w/ the repository URL
3. After Changes Made: `git status`
Expand Down