{"action":"created","issue":{"url":"https://api.github.com/repos/CommBank/ci/issues/40","repository_url":"https://api.github.com/repos/CommBank/ci","labels_url":"https://api.github.com/repos/CommBank/ci/issues/40/labels{/name}","comments_url":"https://api.github.com/repos/CommBank/ci/issues/40/comments","events_url":"https://api.github.com/repos/CommBank/ci/issues/40/events","html_url":"https://github.com/CommBank/ci/pull/40","id":151059903,"number":40,"title":"sbt-ci-build-doc.bsh and docker-version-docs.bsh script","user":{"login":"wrouesnel","id":772445,"avatar_url":"https://avatars.githubusercontent.com/u/772445?v=3","gravatar_id":"","url":"https://api.github.com/users/wrouesnel","html_url":"https://github.com/wrouesnel","followers_url":"https://api.github.com/users/wrouesnel/followers","following_url":"https://api.github.com/users/wrouesnel/following{/other_user}","gists_url":"https://api.github.com/users/wrouesnel/gists{/gist_id}","starred_url":"https://api.github.com/users/wrouesnel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wrouesnel/subscriptions","organizations_url":"https://api.github.com/users/wrouesnel/orgs","repos_url":"https://api.github.com/users/wrouesnel/repos","events_url":"https://api.github.com/users/wrouesnel/events{/privacy}","received_events_url":"https://api.github.com/users/wrouesnel/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/CommBank/ci/labels/in%20progress","name":"in progress","color":"ededed"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-04-26T07:13:11Z","updated_at":"2016-05-01T23:30:42Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/CommBank/ci/pulls/40","html_url":"https://github.com/CommBank/ci/pull/40","diff_url":"https://github.com/CommBank/ci/pull/40.diff","patch_url":"https://github.com/CommBank/ci/pull/40.patch"},"body":"Github pages build scripts. Both leave the details of the final branch push to the CI .yml file, and instead concern themselves with gently getting the project built into a subdirectory while being committed to the appropriate branch.\r\n\r\nTest suites are included for both which provides basic coverage that they run successfully (for sbt this includes building documentation for an included sample project)."},"comment":{"url":"https://api.github.com/repos/CommBank/ci/issues/comments/216081434","html_url":"https://github.com/CommBank/ci/pull/40#issuecomment-216081434","issue_url":"https://api.github.com/repos/CommBank/ci/issues/40","id":216081434,"user":{"login":"wrouesnel","id":772445,"avatar_url":"https://avatars.githubusercontent.com/u/772445?v=3","gravatar_id":"","url":"https://api.github.com/users/wrouesnel","html_url":"https://github.com/wrouesnel","followers_url":"https://api.github.com/users/wrouesnel/followers","following_url":"https://api.github.com/users/wrouesnel/following{/other_user}","gists_url":"https://api.github.com/users/wrouesnel/gists{/gist_id}","starred_url":"https://api.github.com/users/wrouesnel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wrouesnel/subscriptions","organizations_url":"https://api.github.com/users/wrouesnel/orgs","repos_url":"https://api.github.com/users/wrouesnel/repos","events_url":"https://api.github.com/users/wrouesnel/events{/privacy}","received_events_url":"https://api.github.com/users/wrouesnel/received_events","type":"User","site_admin":false},"created_at":"2016-05-01T23:30:42Z","updated_at":"2016-05-01T23:30:42Z","body":"In general nothing which splits out cleanly, beyond trying to unify the git branch management stuff.\r\n\r\nIt also somewhat depends on what the goal of the `gh-pages` branch history is. The current way assumes that history should be rooted in what was current when the commit is pushed. This won't work if branches concurrently push new documentation though since it doesn't do a pull/rebase/merge cycle to update itself before pushing - but, automating that gets ugly real fast anyway since it's not clear what the history means if multiple sources decide to update it simultaneously."}}