aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Rebert <[email protected]>2014-11-20 11:00:34 -0800
committerChris Rebert <[email protected]>2014-11-20 11:00:34 -0800
commit7527ce93c97f37ca078893a90f19bd1e8f6c2702 (patch)
treea47acb4ef2b69a762d32e28d4646f8de86e16f63
parent44735c83bfd9224b0252feab7a12eef9da6ca8c9 (diff)
parent7711c9d60d0dc7db86ac13b200be856409d1d946 (diff)
downloadbootstrap-7527ce93c97f37ca078893a90f19bd1e8f6c2702.tar.xz
bootstrap-7527ce93c97f37ca078893a90f19bd1e8f6c2702.zip
Merge pull request #15187 from twbs/doc-savage-contributing
Document Savage cross-browser JS pull request tester bot [skip sauce]
-rw-r--r--CONTRIBUTING.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9b6627388..871eb6c55 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -199,13 +199,15 @@ included in the project:
**IMPORTANT**: By submitting a patch, you agree to allow the project owners to
license your work under the terms of the [MIT License](LICENSE.md).
-### Pull request checker bot: Rorschach
+### Pull request bots
[@twbs-rorschach](https://github.com/twbs-rorschach) is a Bootstrap bot that hangs out in our GitHub issue tracker and automatically checks all pull requests for a few simple common mistakes. It's possible that Rorschach might leave a comment on your pull request and then close it. If that happens, simply fix the problem(s) mentioned in the comment (there should be link(s) in the comment explaining the problem(s) in detail) and then either:
* Push the revised version to your pull request's branch and post a comment on the pull request saying that you've fixed the problem(s). One of the Bootstrap Core Team members will then come along and reopen your pull request.
* Or you can just open a new pull request for your revised version.
+[@twbs-savage](https://github.com/twbs-savage) is a Bootstrap bot that automatically runs cross-browser tests (via [Sauce](https://saucelabs.com) and Travis CI) on JavaScript pull requests. Savage will leave a comment on pull requests stating whether cross-browser JS tests passed or failed, with a link to the full Travis build details. If your pull request fails, check the Travis log to see which browser + OS combinations failed. Each browser test in the Travis log includes a link to a Sauce page with details about the test. On those details pages, you can watch a screencast of the test run to see exactly which unit tests failed.
+
## Code guidelines