github: fix workflow badge on readme page #489
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The old badge was pointing to the workflows name https://github.com/lightningd/plugins/workflows/Integration%20Tests/badge.svg However this seems to be always failing. Pointing to the workflow file main.yml, which only contains the one integration test workflow, gives a now green badge. I'm not totally into the github internals, so maybe I'm mistaken on this one. Feedback appreciated.
Merged
|
ACK 6a3a997 |
|
Thanks @m-schmoock! Looks snazzy now :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The old badge was pointing to the workflows name
https://github.com/lightningd/plugins/workflows/Integration%20Tests/badge.svg
However this seems to be always failing. Pointing to the workflow file main.yml, which only contains the one integration test workflow, gives a now green badge.
I'm not totally into the github internals, so maybe I'm mistaken on this one. Feedback appreciated.