{"push_id":737485631,"size":4,"distinct_size":1,"ref":"refs/heads/master","head":"099a05024ef4a6e0f23ead21923ec421c6886449","before":"441593fd5f3743ed1daff97b6cf8edca7ed682d0","commits":[{"sha":"93623e2ac84c24e5fc3383fbb215d7cc220432bf","author":{"email":"5f726662e7ca541c0aec63efdec81c7c2711727a@rosetree.de","name":"Micha Rosenbaum"},"message":"Use git data as a fallback (e.g. date of commit)\n\nSome data is saved in the yaml part of the content files and in the git\nrepository. That is redundant and leads to imprecise data (in the yaml\npart and thus in the published data).\n\nNow, the publishing date of an article is defined as the first commit to\nbranch “master”. That way, it’s possible to just don’t declare the\n“created_at” attribute of a post. However, if the attribute is declared\nin the content file, it won’t be overwritten.\n\nSome things are required, that all helpers still work properly.\n\n0. We don’t use functions, but attributes. Most helpers use the data\n   from the yaml part (e.g. “item[:created_at]”) and require the\n   presence of those fields.\n\n1. The data from git is loaded as a preproccessor rule. This ensures,\n   that the data is available before the helpers are loaded.\n\nThanks to the authors of the awesome git library for ruby.\n\nhttps://github.com/schacon/ruby-git","distinct":false,"url":"https://api.github.com/repos/rosetree/plasisent.org/commits/93623e2ac84c24e5fc3383fbb215d7cc220432bf"},{"sha":"a449fe79a7d85b630f0d3996bf28415ab6a7e5e9","author":{"email":"5f726662e7ca541c0aec63efdec81c7c2711727a@rosetree.de","name":"Micha Rosenbaum"},"message":"Use git data to get an author fallback\n\nWhen there isn’t an author associated to the page, the author of the\nfirst commit to the master branch is choosen as a fallback. The used\nfield is `:author_name` as this is used by Nanocs atom feed generation.\n\nAlso display the author on the homepage with the date, so this change\nmakes any sense.","distinct":false,"url":"https://api.github.com/repos/rosetree/plasisent.org/commits/a449fe79a7d85b630f0d3996bf28415ab6a7e5e9"},{"sha":"b2726ec20754be9769e127c9c850285e52f93789","author":{"email":"5f726662e7ca541c0aec63efdec81c7c2711727a@rosetree.de","name":"Micha Rosenbaum"},"message":"Use a single function to add git data\n\nThis improves readability, removes the need for duplicate code\n(retrieving the first commit of a file and commit error handling),\nshould increase performance (commit will only be retrieved once) and\nalso removes error potential as the only function, that can be called,\nhandles everything.","distinct":false,"url":"https://api.github.com/repos/rosetree/plasisent.org/commits/b2726ec20754be9769e127c9c850285e52f93789"},{"sha":"099a05024ef4a6e0f23ead21923ec421c6886449","author":{"email":"5f726662e7ca541c0aec63efdec81c7c2711727a@rosetree.de","name":"Micha Rosenbaum"},"message":"Add commend to make use of git data\n\nThat way authors of blog posts don’t need to write on which date the\npost is published and who wrote it. Those information can be retrieved\nfrom the git log. However, if the data is given in the metadata block,\nthe git data won’t be used.","distinct":true,"url":"https://api.github.com/repos/rosetree/plasisent.org/commits/099a05024ef4a6e0f23ead21923ec421c6886449"}]}