You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Obviously it would be best if the validator rejected this explicitly and the marketplace didn't have entries like this, but the easiest entrypoint I have to feedback is fixing the docs.
The text was updated successfully, but these errors were encountered:
Obviously it would be best if the validator rejected this explicitly and the marketplace didn't have entries like this, but the easiest entrypoint I have to feedback is fixing the docs.
I agree, and I think the best outcome here would be for me to feed back internally about the lack of linting on the Marketplace, as I realise that's frustrating. From a docs perspective, this is a YAML syntax issue above all else and I don't think calling out one specific potential YAML error makes sense, so I'm going to close this out—but please rest assured that I will send that feedback to the Marketplace team. Thank you as ever for your help
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/actions/sharing-automations/creating-actions/publishing-actions-in-github-marketplace
What part(s) of the article would you like to see updated?
The sub-bullets under:
should include
name
should not include:
Additional information
https://github.com/marketplace/actions/nowsecure-mobile-sbom is a composite action on the marketplace
it corresponds to:
https://github.com/nowsecure/nowsecure-sbom-action/blob/main/action.yml
Clicking
Use latest version
yields:https://github.com/check-spelling-sandbox/stunning-bassoon/actions/runs/13566473746
https://github.com/check-spelling-sandbox/stunning-bassoon/actions/runs/13566473746/workflow
Obviously it would be best if the validator rejected this explicitly and the marketplace didn't have entries like this, but the easiest entrypoint I have to feedback is fixing the docs.
The text was updated successfully, but these errors were encountered: