From 31624d3461bc8ee6a0fbae697683f9197548d13e Mon Sep 17 00:00:00 2001 From: Chris Rebert Date: Tue, 19 Jan 2016 16:58:29 -0800 Subject: README: Hyperlink license badge --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 78d0b26..4342246 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ Savage ====== [![Build Status](https://travis-ci.org/twbs/savage.svg?branch=master)](https://travis-ci.org/twbs/savage) ![Development Status :: 4 - Beta](https://img.shields.io/badge/maturity-beta-yellowgreen.svg "Development Status :: 4 - Beta") -![MIT License](https://img.shields.io/badge/license-MIT-blue.svg "MIT License") +[![MIT License](https://img.shields.io/badge/license-MIT-blue.svg "MIT License")](https://github.com/twbs/savage/blob/master/LICENSE.txt) Savage is a service that 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 [public members](https://help.github.com/articles/publicizing-or-hiding-organization-membership/) 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: "@\ retry" (e.g. "@twbs-savage retry") -- cgit v1.2.3