Thanks for the PR but we're not interested in this tag at this time. Have a great day!

@MikeMcQuaid I however am!
It would greatly reduce time to lookup build output from a commit.
Could you elaborate on why there is no interest in the badge?

@Shredder121 Can you describe your use-case? Thanks!

@Shredder121 Yea this is better, because I think the one I had was static, but not sure if it was.

Add a line note

[![Build Status](https://travis-ci.org/github/developer.github.com.svg?branch=master)](https://travis-ci.org/github/developer.github.com) Add a line note

@MikeMcQuaid Every now and then I visit thebranches overview of Travis.
This lists in a nutshell the few latest builds on master. (which indicate the stability of the build)
For example, if it weren't for commit8b0528e, I'd have submitted a PR for it.

Basically, to get to the branches overview, you either have to bookmark it, or you can click through to it via a PR, but to get to a PR it requires a lot of clicks counting from the GitHub Homepage.

• Click the repo in the 'Repositories you contribute to' panel
• Click thepull requests tab
• Pick one (maybe there are no open ones)
• Scroll to pull request status, click travis build
• Clickbranches tab

Compare that to:

• Click the repo in the 'Repositories you contribute to' panel
• Click the Travis badge (which already shows an indication of the stability)
• Clickbranches tab

Even more actions when on mobile, but it happens.

I just appreciate developer resources to be in a common place. Even developer resources for a developer resource.

I hope any of this makes sense.

Ok, seems reasonable, thanks!

@jtrent238 Thanks for your contribution. You rock!

@jtrent238 Yes you rock!