Fork me on GitHub

Third Class Notes

by Elliott Hauser

28 Aug 2013

Wednesday Aug 28th Readings:

  1. Comoyo: How we built our company blog - Evidence that what we’re doing isn’t totally out of left field. For bonus points, dig into some of the source code of their site.

  2. Software Carpentry: Computational Thinking - This is intended as a wrap-up essay but I often find it useful to ‘start at the end’. Use the essay to orient yourself to concepts that we’ll be learning.

  • [ ] In-Class Exercise: Write a simple post with syntax highlighting.

Mini lecture: Github roundup

  • A pull request is a wrapper around branch diffs
  • #140
  • "Fixes #134" is the magic phrase that closes issues
  • Look for examples!
  • We'll have more control over the flow from the command line
  • Milestones = assignments
  • One issue per assignment, please. Multiple PRs OK, just keep track of them.
  • post ideas
  • Michelle's forking question.

Left over from last time: How Jekyll works

  • _config.yml: Where sitewide variables live
  • _posts/: Where posts live
  • _layouts/: HTML for Jekyll to instert our content into
  • *.markdown: Pages for the site

  • [x] In-Class Exercise: Open your first pull request

  • [x] In-Class Exercise: Close your first pull request

  • [x] In-Class: Pair up with your merging partner.

  • [ ] In-Class: Set up VirtualBox Ubuntu. Extra credit for helping peers install outside of class. This is due by the end of the week. Post to our Google community if you're having trouble setting it up and someone will help you out.

Elliott Hauser is a PhD Student in information science at UNC Chapel Hill. He's hacking education as one of the cofounders of Coursefork.org. Find Elliott Hauser on Twitter, Github, and on the web.
comments powered by Disqus