-
Notifications
You must be signed in to change notification settings - Fork 20
docs(README): Use shields.io to fix broken badges #189
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.
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
Conversation
GitHub badges require authentication for projects that one is a member of. Members of the project who should really see these badges will have to login with GitHub before seeing these. Use shields.io as a badge proxying and caching service. Use this opportunity to modernize the badge and list the mainline builds. Signed-off-by: Loïc Minier <[email protected]>
Test Results 3 files ±0 7 suites ±0 15m 57s ⏱️ ±0s For more details on these failures, see this check. Results for commit 6e3b14e. ± Comparison against base commit 1b72a72. |
Test jobs for commit 6e3b14e |
|
(Test failures were for a previous test run on RB1 that was given back; and we don't need LAVA/boot tests for this change.) |
|
Will shields.io have access to actions? I think this is the tricky bit. Github asks me to authenticate if I want to see actions. |
Yeah, you can try the URLs with img shield, they work in e.g. an incognito window :) |
GitHub badges require authentication for projects that one is a member of. Members of the project who should really see these badges will have to login with GitHub before seeing these. Use shields.io as a badge proxying and caching service. Largely based on qualcomm-linux/qcom-deb-images#189 Suggested-by: Loïc Minier <[email protected]> Signed-off-by: Nicolas Dechesne <[email protected]>
GitHub badges require authentication for projects that one is a member of. Members of the project who should really see these badges will have to login with GitHub before seeing these. Use shields.io as a badge proxying and caching service. Largely based on qualcomm-linux/qcom-deb-images#189 Suggested-by: Loïc Minier <[email protected]>

GitHub badges require authentication for projects that one is a member
of. Members of the project who should really see these badges will have
to login with GitHub before seeing these. Use shields.io as a badge
proxying and caching service.
Use this opportunity to modernize the badge and list the mainline
builds.