{"action":"created","issue":{"url":"https://api.github.com/repos/CommBank/ci/issues/12","labels_url":"https://api.github.com/repos/CommBank/ci/issues/12/labels{/name}","comments_url":"https://api.github.com/repos/CommBank/ci/issues/12/comments","events_url":"https://api.github.com/repos/CommBank/ci/issues/12/events","html_url":"https://github.com/CommBank/ci/pull/12","id":113971490,"number":12,"title":"Allow a branch to `export IS_RELEASE=0` to force-publish","user":{"login":"lancelet","id":356739,"avatar_url":"https://avatars.githubusercontent.com/u/356739?v=3","gravatar_id":"","url":"https://api.github.com/users/lancelet","html_url":"https://github.com/lancelet","followers_url":"https://api.github.com/users/lancelet/followers","following_url":"https://api.github.com/users/lancelet/following{/other_user}","gists_url":"https://api.github.com/users/lancelet/gists{/gist_id}","starred_url":"https://api.github.com/users/lancelet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lancelet/subscriptions","organizations_url":"https://api.github.com/users/lancelet/orgs","repos_url":"https://api.github.com/users/lancelet/repos","events_url":"https://api.github.com/users/lancelet/events{/privacy}","received_events_url":"https://api.github.com/users/lancelet/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-10-29T03:28:30Z","updated_at":"2015-10-29T04:50:10Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/CommBank/ci/pulls/12","html_url":"https://github.com/CommBank/ci/pull/12","diff_url":"https://github.com/CommBank/ci/pull/12.diff","patch_url":"https://github.com/CommBank/ci/pull/12.patch"},"body":"Ping @stephanh, @SamRoberts.\r\n\r\n  - Currently, there is a hard-coded list of branches that are\r\n    published (see settings.sh). This change allows a .travis.yml\r\n    file to `export IS_RELEASE=0;`, which would then force that\r\n    branch to be published.\r\n  - This is a possible solution to Issue #11. Please feel free to\r\n    comment / suggest an alternative approach. Right now, it's\r\n    just a very minimal change to an existing variable that is\r\n    currently used for this purpose."},"comment":{"url":"https://api.github.com/repos/CommBank/ci/issues/comments/152075334","html_url":"https://github.com/CommBank/ci/pull/12#issuecomment-152075334","issue_url":"https://api.github.com/repos/CommBank/ci/issues/12","id":152075334,"user":{"login":"luke-clifton","id":6327304,"avatar_url":"https://avatars.githubusercontent.com/u/6327304?v=3","gravatar_id":"","url":"https://api.github.com/users/luke-clifton","html_url":"https://github.com/luke-clifton","followers_url":"https://api.github.com/users/luke-clifton/followers","following_url":"https://api.github.com/users/luke-clifton/following{/other_user}","gists_url":"https://api.github.com/users/luke-clifton/gists{/gist_id}","starred_url":"https://api.github.com/users/luke-clifton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/luke-clifton/subscriptions","organizations_url":"https://api.github.com/users/luke-clifton/orgs","repos_url":"https://api.github.com/users/luke-clifton/repos","events_url":"https://api.github.com/users/luke-clifton/events{/privacy}","received_events_url":"https://api.github.com/users/luke-clifton/received_events","type":"User","site_admin":false},"created_at":"2015-10-29T04:50:10Z","updated_at":"2015-10-29T04:50:10Z","body":"Wouldn't it be better to track this outside of the repository itself... doesn't really seem like it should belong in there (why do I need to touch repository to get it released). Travis lets you set per project environment variables. I propose that we use such an environment variable to extend the list of branches that are to be released.\r\n\r\nPros:\r\n * This lets you see in one place which branches are getting released (rather than having to look in every branch)\r\n * I can momentarily add a branch, rebuild it, and remove it again to get a point release for a particular branch (which, given the motivation for this change, a demo, seems like a good feature)\r\n * Don't dirty the history with \"meaningless\" commits to toggle releases on and off.\r\n * No need to worry about changing things before merging with master\r\n\r\nCons:\r\n * Not in source control could be considered a con?"}}