Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Automatic detection of repo and branch for badges #1892

Closed
defunctzombie opened this issue Jan 25, 2014 · 4 comments
Closed

Automatic detection of repo and branch for badges #1892

defunctzombie opened this issue Jan 25, 2014 · 4 comments

Comments

@defunctzombie
Copy link

By looking at the Origin header, travis badge images on readmes could autodetect the repo and branch. This would be very helpful for long lived project branches and pull requests. Instead of hard coding the repo and branch in the image url, a generic image url would suffice. Now when a fork or branch happens, the README doesn't need to be updated in order to see the status of that particular branch/fork. This helps avoid confusion about what is actually passing and what isn't.
@sarahhodne
Copy link
Contributor

Thank you for the feature request. This has already been suggested in #974 and #779, so I'm going to close this, please feel free to subscribe to those.

jkremser added a commit to jkremser/hawkular that referenced this issue Jul 20, 2015
@jkremser
travis shows red badge on the GitHub readme even if some build for ot…
21ab7d3 
…her branch fails, in my opinion and in ideal world the badge should show the status of the branch I am looking at in the GitHub, unfortunatelly it's not currently possible (travis-ci/travis-ci#1892). So at least let's make the icon mean the status of the last build for master branch, and not 'status of the last build of any branch'
@jkremser jkremser mentioned this issue Jul 20, 2015
Merged
jkremser added a commit to jkremser/hawkular-inventory that referenced this issue Jul 20, 2015
@jkremser
travis shows red badge on the GitHub readme even if some build for ot…
2348f2f 
…her branch fails, in my opinion and in ideal world the badge should show the status of the branch I am looking at in the GitHub, unfortunatelly it's not currently possible (travis-ci/travis-ci#1892). So at least let's make the icon mean the status of the last build for master branch, and not 'status of the last build of any branch'
@jkremser jkremser mentioned this issue Jul 20, 2015
Merged
@MarkCallow
Copy link

Both the issues referred to here, #974 & #779 have been closed due to apparent issues with the suggested Referrer header. This has been closed as well so where is this problem now being discussed.

A solution is sorely needed. I have long-lived incoming and master branches and the requirement for explicit links in the README is causing massive merge headaches.

@jonathanperret jonathanperret mentioned this issue Mar 3, 2016
Merged
@Quuxplusone Quuxplusone mentioned this issue Jun 26, 2018
Merged
@0bsearch
Copy link

0bsearch commented Jul 3, 2018

Any news on this?

@jonbergh jonbergh mentioned this issue Jul 26, 2018
Closed
This was referenced Oct 22, 2018
Closed
Closed
@rishichawda
Copy link

@3lnc I ended up making a plugin and using it on githooks. Hope this helps you as well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@sarahhodne @defunctzombie @0bsearch @MarkCallow @rishichawda