diff options
| author | Chris Rebert <github@rebertia.com> | 2014-12-10 02:04:25 +0300 |
|---|---|---|
| committer | Chris Rebert <github@rebertia.com> | 2014-12-10 02:04:25 +0300 |
| commit | 87c3beb48404c8ee7d5b35bd04ada8122b011c0c (patch) | |
| tree | b336669e8238f40a8c68957108eff0877a6b4b3c | |
| parent | af05256f30dcc332b3a9d28681839816a2c5f156 (diff) | |
Update README.md
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -5,7 +5,7 @@ Savage Savage is a service watches for new or updated pull requests on a given GitHub repository. For each pull request, it evaluates whether the changes are "safe" (i.e. we can run a Travis CI build with them with heightened permissions without worrying about security issues) and "interesting" (i.e. would benefit from a Travis CI build with them with heightened permissions), based on which files were modified. If the pull request is "safe" and "interesting", then it initiates a Travis CI build with heightened permissions on a specified GitHub repository. When the Travis CI build completes, it posts a comment ([like this one](https://github.com/twbs/bootstrap/pull/15178#issuecomment-63756231)) with the test results on the pull request. If the test failed, the pull requester can then revise their code to fix the problem. Users who are members of trusted GitHub organizations (see the `trusted-orgs` setting) can ask Savage to retry a pull request by leaving a comment on the pull request of the form: "@\<username-of-savage-bot> retry" (e.g. "@twbs-savage retry") -Savage's original use-case is for running Sauce Labs cross-browser JS tests on pull requests via Travis CI, while keeping the Sauce Labs access credentials secure. +Savage's original use-case is for running Sauce Labs cross-browser JS tests on pull requests via Travis CI, while keeping the Sauce Labs access credentials private & secure. Affectionately named after an experimenter known for "busting" misconceptions, often with explosives. |