{"push_id":626394068,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"10e7d2cf22a737d35c63c9e59eac12045e350499","before":"3cea958e9facb1703fd96655f350561864c6dd9a","commits":[{"sha":"10e7d2cf22a737d35c63c9e59eac12045e350499","author":{"email":"08fcb62a68e73582707673d0bde6fd693e62e327@livingsocial.com","name":"Dave Woodall"},"message":"git:toc\t\n\nThe best way to learn is to build. There’s so much learning in a specific commit message that I started wishing I could just convert this commit into a blog post. But the problem there is I have to context switch, reformat, and now maintain a separate project. So, that gave me a new idea. What if I converted my commits into a table of contents based on titles that I’m learning in the project. \n\nI never really thought of using this space beyond a single line and link to a jira ticket. But what if this is the section to write a post? So, here I am writing a post in the commit message. \n\n# git:toc\nThis can be accomplished by doing a few things as are added in this commit;\n\n## config/*.yml\nPut the title and other configs I want to add to the table of contents\n\n## rake tasks\nList out the table of contents with `rake git:toc`\nI envision a `git:publish` that will convert info into a `index.html` page\n\n### Example Output\nLearning Ruby\nI had wanted to learn more about specific methods\n07b9657 The difference between #map and #select\n\nSetting up Capybara\nI want to get do end to end testing\n1fdb874 Trying to get Capybara’s #page method, but not successful\n35969a0 Add minitest & capybara via minitest-rails-capybara\n0b040c2 Capybara works, yay!","distinct":true,"url":"https://api.github.com/repos/woodall/HashPageMe/commits/10e7d2cf22a737d35c63c9e59eac12045e350499"}]}