-
Notifications
You must be signed in to change notification settings - Fork 214
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
Add github.com as badge provider #389
Comments
Since 84f537a there is no more whitelist. Please update to the latest vsce. |
@joaomoreno Well, when i had GitHub badges it stated that it was an invalid badge. I will try again next week and create another issue if it occurs again. Cheers |
@joaomoreno All these doc articles does not reflect the fact that the badges are not whitelisted anymore. And this part of the doc , actually states the problem I have now: |
@andreujuanc Thanks for the ping. We've actually just had a discussion yesterday in the team that this list should be brought back: #395 I will fix it asap and release a new VSCE version. |
@andreujuanc Can you show me an example badge from Github? |
Sorry for the delay @joaomoreno it was a busy day.
Thanks for reopening this, it'd be really cool to show the badge :) |
We can't add that source as a trusted badge provider, since this would enable anyone to simply use any badge by simply uploading it to Github. |
Hm... I see that's actually the Actions badge. We might need to improve the pattern here, since we currently filter on domain only. So we're currently blocked by the Marketplace first and then by VSCE. |
Reference to all the possible badge URLs |
@joaomoreno had to remove my badges as well 😞@joaomoreno do you know what security concerns warrant a whitelist? I haven't seen other package/plugin discovery platforms have this requirement. |
Otherwise we are unable to publish a new version of the extension: microsoft/vscode-vsce#389 (comment) also very small elixir-ls update
Work around microsoft/vscode-vsce#389. Currently, we can't use SVG shields directly from github.com, so let's temporarily use whitelisted img.shields.io.
@joaomoreno what's the long term plan here? |
It's to resolve the issue. 👍 Still waiting on the upstream Marketplace implementation. |
That's not a public issue we can follow, right? |
Unfortunately right, but I can tell you it's getting done! |
This is finally in! Both the server side changes and VSCE changes were deployed. Starting with vsce@1.77.0, you can now use github workflow badges. |
Now with Github Actions having badges, we've got a new provider to add to the whitelist.
I'm removing my badges for now.
The text was updated successfully, but these errors were encountered: