Intro to
for everyone!
What is Git
Git is version control.
What is GitHub
A website that uses Git.
So where does this fit into my design process?
Think of Github as a project managment platform.
converse
decide
Update
See progress
Contribute to the codebase
Parts of a Github Repo
Repo Files
Home of your project files.
Wiki
Work in progress information.
Issues
Actionable tasks that need to be completed.
Labels
Tags to add to issues.
Milestones
Collection of Issues with a deadline.
Pull-Requests
Files you want merged into the repo.
Issues
This is where most of the work happens.
This is what a common issue thread looks like.
How to Work with Issues
Share EVERYTHING within the related issue - post updates, comps, roadblocks, real-life discussions, etc.
Issues work use Markdown.
Images are supported just DRAG AND DROP!
You can reference other issues that might be roadblocks to progress.
You can add checkboxes to your issue of tasks that need to be completed - You can see this progress on the outside!
Tag people with @name
Rules of Issues
- Issues are worded as a deliverable
- Never close issues without a Pull Request that relates
- Never close your OWN Issue or Pull Request! - Always have someone else look it over before
Worded as a deliverable
Never Close without a related Pull Request
:thumbsup: FOR APPROVAL
Milestones
Milestones are a way to track progress of a project
- Link issues to milestones
- Set Deadlines
- See Progress!
Waffle.IO
Wiki vs. Repo
Wiki
Wiki is where we will work on the content.
- Abstracted User Research
- Copywriting for Product
- Information Architecture
- Final Documentation that doesn't live in the codebase
- Lexicon
- etc.
Repo
Repo is where the code base lives.
- Final Copy for Product
- Final Documentation for the codebase
- Code
Contributing to the Repo
- Fork Project and Create a pull request from your fork.
- NEVER PUSH TO MASTER! EVER!
- Create a branch named with what you are working.