{"action":"closed","issue":{"url":"https://api.github.com/repos/macrojc/macrojc/issues/3","labels_url":"https://api.github.com/repos/macrojc/macrojc/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/macrojc/macrojc/issues/3/comments","events_url":"https://api.github.com/repos/macrojc/macrojc/issues/3/events","html_url":"https://github.com/macrojc/macrojc/issues/3","id":56602295,"number":3,"title":"Joseph's issue from the old repo","user":{"login":"nhcooper123","id":5993462,"avatar_url":"https://avatars.githubusercontent.com/u/5993462?v=3","gravatar_id":"","url":"https://api.github.com/users/nhcooper123","html_url":"https://github.com/nhcooper123","followers_url":"https://api.github.com/users/nhcooper123/followers","following_url":"https://api.github.com/users/nhcooper123/following{/other_user}","gists_url":"https://api.github.com/users/nhcooper123/gists{/gist_id}","starred_url":"https://api.github.com/users/nhcooper123/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nhcooper123/subscriptions","organizations_url":"https://api.github.com/users/nhcooper123/orgs","repos_url":"https://api.github.com/users/nhcooper123/repos","events_url":"https://api.github.com/users/nhcooper123/events{/privacy}","received_events_url":"https://api.github.com/users/nhcooper123/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-04T23:09:33Z","updated_at":"2015-02-04T23:12:34Z","closed_at":"2015-02-04T23:12:34Z","body":"I know it's bad practice to do this, but figured it might be useful to have this in the audit trail for this repo too...\r\n\r\n***\r\nY'All,\r\n\r\nI (eventually, and with non-negligible hair-pulling, leaving a horrendous commit history in my wake) came upon the reason why pushed edits were not being displayed.\r\n\r\nApparently (and this was not easily found) there are two types of GitHub Pages:\r\n\r\nTypical \"Organization\" repos (named: <orgname>/github.io) that are in place solely for serving web content (comme ça) must have the content on the master branch (and served on the site: https://<orgname>.github.io).\r\n\r\nOn the other hand, \"Project Pages\" (named: <orgname>/<projectname>) have actual code on master, and web content on a branch named gh-pages (served on: <orgname>.github.io/<projectname>).\r\n\r\nHence the problem: @wrightaprilm set up sweet code to generate and push html content to the branch gh-pages, but given that this is an \"Organization\" repo, the site (http://macrojc.github.io) reads only from the master branch. It looks like everything was working correctly (i.e. edits were properly pushed to the gh-pages branch), it is just that the site was instead reading content from master.\r\n\r\nYeesh.\r\n\r\nAnyway, two possible solutions:\r\n\r\nGet rid of the gh-pages branch, and do everything on master.\r\nCreate a \"project\" for the organization, set up exactly as the current repo is (i.e. with two branches). This way, all of @wrightaprilm's work behaves as expected (e.g. creating content on master, pushing generated html to gh-pages).\r\n\r\nI experimented with the latter. I created a repo (https://github.com/macrojc/macrojc) that has all of the code from the present site (although this issue did not make the migration, for whatever reason). Things work fine: create a new post or whatever, and then do:\r\n```\r\nmake github\r\n```\r\nand things are pushed to gh-pages and appear on the website (http://macrojc.github.io/macrojc/). Wee!\r\n\r\nAnywho, use the new repo, or fix the current one; I was just playing around. I did make a new post, and updated the papers read page, tho."}}