Based on: [https://docs.google.com/document/d/16Zr-IZWm_g8SBop-Nqs6UkIXzGauI9nkhViEhVRfcZo/edit?usp=sharing], And: [https://guides.github.com/activities/hello-world/]
Git is a version control system used for tracking changes in software.
GitHub is a web-based Git or version control repository and Internet hosting service. It provides access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project.
Keeping track of documentation is doubly-important. Github is a central place where documentation can be kept and updated, and it has version control baked in.
A place where you can store information about a project. It can contain folders and files, images, videos, spreadsheets, and data sets – anything, really. A good practice to get into is to add a README, or a file with information about your project when you start your repository. This is also where you can add license information, should you want to add a license to your work.
Branching is the way to work on different versions of a repository at one time.
The master branch is is considered to be the definitive branch. Use branches to experiment and make edits before committing them to master. When you create a branch off the master branch, you’re making a copy, or snapshot, of master as it was at that point in time. If someone else made changes to the master branch while you were working on your branch, you could pull in those updates.
Pull Requests are the heart of collaboration on GitHub. When you open a pull request, you’re proposing your changes and requesting that someone review and pull in your contribution and merge them into their branch. Pull requests show diffs, or differences, of the content from both branches. The changes, additions, and subtractions are shown in green and red.
Contributing to someone else’s project or using it as a basis to start your own.
Creating a “fork” is producing a personal copy of someone else’s project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit Pull Requests to help make other people’s projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub.
https://guides.github.com/activities/forking/
Hello, world… https://guides.github.com/activities/hello-world/
Practice exercises:
Adding documentation to the ScholarWorks repository (maybe a test SW repository?)
https://codeburst.io/number-one-piece-of-advice-for-new-developers-ddd08abc8bfa
https://codeburst.io/a-step-by-step-guide-to-making-your-first-github-contribution-5302260a2940
Resources and things to read: