Before we even start to type a single line of code, we'll need to set-up your environment with the following tools:
A code hosting platform for version control and collaboration, where developers can store and share their projects.
Some commonly used terms that we'll be using in class:
https://help.github.com/articles/github-glossary/
Repository -The location where all the files for a particular project are stored
Fork - Creating a personal copy of someone else's project.
Clone - Making a copy of the repo into your local computer. This repo copy lives on your computer instead of on website’s server.
Pull Requests - When you fork a repo, make a revision to the project and want to be recognized by the original developer, you can create a pull request, so the author of the original repository can see your work and decide whether or not to accept it into the official project.
Share (slack) your Github handle with the team
Follow your team members in Github
Fork the following repository:
https://github.com/octocat/Spoon-Knife
git status - list all new or modified files to be committed
git add filename - snapshots the file in preparation for versioning
git commit -m “descriptive message” - records file snapshots permanently in version history
Version Control Workflow
A text editor for code, markup and prose.
1. Fork repo
DevLeague's Github Repo
Your Github Repo
Your Awesome Computer
2. Clone repo into your machine
3. Make changes to the file
4. Save and Commit your code
5. Push updated file into your repo
6. Pull request