1 / 17

Fork this Repo!

GitHub 102 Tutorial. Fork this Repo!. Tutorial Session - Web Experience Toolkit CodeFest 2014 August 14 & 15 2014 Justin Longo – PostDoc in Open Governance Center for Policy Informatics, Arizona State University slides etc. available at http://jlphd.wordpress.com

bunme
Download Presentation

Fork this Repo!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GitHub 102 Tutorial Fork this Repo! Tutorial Session - Web Experience Toolkit CodeFest 2014 August 14 & 15 2014 Justin Longo – PostDoc in Open Governance Center for Policy Informatics, Arizona State University slides etc. available at http://jlphd.wordpress.com Twitter: #GitHub102 @whitehallpolicy

  2. Learning Objectives • Copy a repo to your account • Contribute to other repos • Flag an issue • Issue a pull request • Manage a pull request • Create your GitHub webpage

  3. Fork a Repo • To fork a project, just go to the repo you’re interested in, and click the “Fork” button. • For example, go to https://github.com/wet-boew/wet-boew and click “Fork”

  4. Fork a Repo And a few seconds later, and the repo is now magically in your account: This is a full copy that you can edit as you want without affecting the original.

  5. Fork a Repo You can see how many forks a popular repo has:

  6. Flag an Issue Go to test site: http://bit.ly/githubcinderella. Click on the Issues Icon: On the next page, click on the green “New Issue” button.

  7. Flag an Issue To complete the issue flag, you would describe the issue (title, message), assign someone responsible, add a label and then click on “Submit new issue”. The owner will review the issue and respond.

  8. Flag an Issue Issues can get very detailed. Here’s the start of a very fun issue comment thread with over 700 comments) related to the October 2013 U.S. government shutdown (you can find it at http://bit.ly/govshutdowngithub).

  9. Pull Requests: Making a Simple Contribution To propose a change to someone else’s file, navigate to the page you want to change and click on the pen icon You will see this notice: By editing directly through the GitHub.com interface, you are quickly borrowing a copy of the master. This is a simple way of proposing a change. No need to “Fork the Repo” to propose a simple change.

  10. Pull Requests: Making a Simple Contribution Enter any changes you want to propose: When you’re done, scroll to the bottom of the page, label your change and describe it, and then click on “Propose file change”

  11. Pull Requests: Making a Simple Contribution On the next page you'll see this: Your title and description are brought over from the previous page. Click on “Send pull request”. The owner of the file will receive your suggested changes.

  12. Managing Pull Requests • If someone else sends you a pull request, you’ll receive a notification. • Navigate to the open issue and review what was proposed. • Once you’re satisfied with the pull request – and if it can be automatically merged – click the "Merge pull request" button, enter a commit message and click "Confirm merge”. • This button merges the pull request into the original, sends a notification to the person who initiated the pull request, and closes the pull request.

  13. Create your GitHub Webpage • First, you need to create a special repo in your account dedicated to only the Pages files. • On your profile page, in the top-right corner, select the + icon and click on “New repository” to get to this page: • choose a “Repository name”. You must use the username/username.github.io naming scheme • write a short description (“My GitHub webpage” works) • mark the repo as “Public” • mark the check-box “Initialize this repository with a README” • “.gitignore” = None • <-- Licence = CC0 1.0 Universal (Creative Commons). • <-- Click on “Create Repository”.

  14. Create your GitHub Webpage • Go to the main page for this dedicated repo you just created, and then click on “Settings” in the right-hand column. • Scroll down to “GitHub Pages” and click on the magical “Automatic Page Generator” button. • You’ll see a page like this: • <-- Edit the page name and tagline • <-- Edit the page body • <-- Click on “Continue to layouts”.

  15. Create your GitHub Webpage • Pick your favorite layout and click on the green “Publish page” box to publish your page. • You’ll find your awesome page at http://yourusername.github.io • (It may take up to ten minutes to show up.) • Edit the file index.html to pretty-up the home page.

  16. Exercises for Later • Fork some more repos • Contribute to other repos • Flag an issue • Issue a pull request • Manage a pull request • Edit your GitHub webpage • Check out “Jekyll and Github Pages” with Shawn Thompson – Friday at 2 pm http://wet-boew.github.io/codefest/sessions-en.html#shawnt-session-title • Continue to explore GitHub

  17. Tutorial Notes • Slides, project posts, my contact info:http://jlphd.wordpress.com • Government GitHub User Survey: http://bit.ly/githubsurvey • Online Tutorial: http://nextpolicychallenge.github.io/tutorial.html • GitHub Glossary (GitHub version): https://github.com/NextPolicyChallenge/NextPolicyChallenge.github.io/blob/master/glossary.md

More Related