{"action":"created","issue":{"url":"https://api.github.com/repos/AmpersandJS/ampersand-select-view/issues/35","labels_url":"https://api.github.com/repos/AmpersandJS/ampersand-select-view/issues/35/labels{/name}","comments_url":"https://api.github.com/repos/AmpersandJS/ampersand-select-view/issues/35/comments","events_url":"https://api.github.com/repos/AmpersandJS/ampersand-select-view/issues/35/events","html_url":"https://github.com/AmpersandJS/ampersand-select-view/issues/35","id":61974113,"number":35,"title":"SauceLabs tests won't run on Pull Requests","user":{"login":"nickryall","id":209703,"avatar_url":"https://avatars.githubusercontent.com/u/209703?v=3","gravatar_id":"","url":"https://api.github.com/users/nickryall","html_url":"https://github.com/nickryall","followers_url":"https://api.github.com/users/nickryall/followers","following_url":"https://api.github.com/users/nickryall/following{/other_user}","gists_url":"https://api.github.com/users/nickryall/gists{/gist_id}","starred_url":"https://api.github.com/users/nickryall/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nickryall/subscriptions","organizations_url":"https://api.github.com/users/nickryall/orgs","repos_url":"https://api.github.com/users/nickryall/repos","events_url":"https://api.github.com/users/nickryall/events{/privacy}","received_events_url":"https://api.github.com/users/nickryall/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-03-16T05:13:46Z","updated_at":"2015-03-16T05:41:33Z","closed_at":null,"body":"@bear @cdaringe\r\n\r\nI 'think' the issue with Sauce Labs may be that because the travis.yml is using the secure access key, only users with write access to the repo will be able to have the tests run on forked PRs. \r\n\r\nIn summary the solution is to either use the public keys in the travis.yml ( which would make the account prone to abuse  e.g. using it to run tests on other projects ) or using something like this:\r\n\r\nhttps://github.com/twbs/savage\r\n\r\nRelated discussion can be found here:\r\n\r\nhttps://support.saucelabs.com/entries/25614798-How-can-we-set-up-an-open-source-account-that-runs-tests-on-people-s-pull-requests-\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/AmpersandJS/ampersand-select-view/issues/comments/81431563","html_url":"https://github.com/AmpersandJS/ampersand-select-view/issues/35#issuecomment-81431563","issue_url":"https://api.github.com/repos/AmpersandJS/ampersand-select-view/issues/35","id":81431563,"user":{"login":"cdaringe","id":1003261,"avatar_url":"https://avatars.githubusercontent.com/u/1003261?v=3","gravatar_id":"","url":"https://api.github.com/users/cdaringe","html_url":"https://github.com/cdaringe","followers_url":"https://api.github.com/users/cdaringe/followers","following_url":"https://api.github.com/users/cdaringe/following{/other_user}","gists_url":"https://api.github.com/users/cdaringe/gists{/gist_id}","starred_url":"https://api.github.com/users/cdaringe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cdaringe/subscriptions","organizations_url":"https://api.github.com/users/cdaringe/orgs","repos_url":"https://api.github.com/users/cdaringe/repos","events_url":"https://api.github.com/users/cdaringe/events{/privacy}","received_events_url":"https://api.github.com/users/cdaringe/received_events","type":"User","site_admin":false},"created_at":"2015-03-16T05:41:33Z","updated_at":"2015-03-16T05:41:33Z","body":"interesting concept.  we could also just start merging into a `develop` branch vs master, and if the build fails, in develop, the maintainer could revert the merge commit?  that sure is undue overhead for the maintainer.  perhaps if we merged into a develop branch, then post--CI *tests-pass*, some hook could listen and merge that commit into master?  That's gotta be doable?  on *tests-fail* it should revert the commit too, that way multiple PRs hitting the develop branch at once wouldn't get merged into master together."}}