INTRO TO GITHUB How to become a sir while githubbing
AGENDA Let’s assume you have your Git-Fu down. • GitHub Workflow • Branch • Commit • Pull Request • Discuss and Review • Merge and Deploy • Let’s Do it For Reals: • <Insert Live Demo Here> • Forking • Pull Requests • Issues
GITHUB WORKFLOW Yeah, it’s that simple.
CREATE A BRANCH git checkout -b “monocles-for-everyone”
PRO-TIP Anything on the master branch is ALWAYS deployable to production. mmm so high-res :shipit:
ADD SOME COMMITS git commit -m “so many monocles”
GIT COMMIT -M PRO-TIP “FIXED ERRORS IN Write clear commit messages THE PREVIOUS so that people know what the hell you’re doing. COMMIT”
OPEN A PULL REQUEST You’re well on your way to GitHub sir-ism
PRO-TIP 1) Use ‘@mention’! 2) Use Fork/Pull model for open source repos to notify maintainers! 3) Use Pull requests to help start a conversation with your group, if repo is shared!
FORK? ‘SPLAIN YOURSELF. A fork is an exact copy of a repository. Use it to run experiments without screwing anything up.
VS FORK > BRANCH? well it depends on what you’re doing.
DISCUSS AND REVIEW CODE Remember, we’re collaborating here.
PRO-TIP Pull request comments support emojis :thumbsup:
MERGE AND DEPLOY You’ve done it, sir.
PRO-TIP I <3 DOCS Secret keywords do cool stuff in commit messages: “created landing page Closes #32”
A QUICK REVIEW Someone explain this to me.
LIVE DEMO Let’s hope this guy knows what he’s doing…