Publishing actions in GitHub Marketplace appears to wrongly suggest Each repository must contain a single action

[jsoref]

Code of Conduct

• I have read and agree to the GitHub Docs project's 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?

Actions are published to GitHub Marketplace immediately and aren't reviewed by GitHub as long as they meet these requirements:

• The action must be in a public repository.
• Each repository must contain a single action.

I'm not sure this is a real requirement... At the very least, the GitHub Actions organization violates this:

• actions/cache ... restore/action.yml
• actions/upload-artifact ... merge/action.yml
• actions/attest-build-provenance ... predicate/action.yml
• actions/cache ... save/action.yml
• actions/github-script ... install-dependencies/action.yml
• actions/versions-package-tools ... actions/send-slack-notification/action.yml

GitHub codeql-action definitely doesn't conform to this:

• init
• analyze
• autobuild
• start-proxy
• resolve-environment
• upload-sarif

At least Endor Labs Scan has multiple action.yml files

• GitHub Action for Go Fuzz has two
• Diffblue Cover Pipeline has four
• DataDog Synthetics Action has one
• Infisical Loader has one
• Tree-sitter parser tests has five
• Zeet Deploy has one

I certainly haven't seen anything preventing it.

Additional information

No response

[nguyenalex836]

@jsoref Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛

[github-actions]

Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀

[github-actions]

This is a gentle bump for the docs team that this issue is waiting for technical review.

[nguyenalex836]

@jsoref Thank you for your patience while our SME team reviewed! They provided the following responses:

I don’t think this is valid, the customer is questioning that the actions exist without meeting the stated requirements but the stated requirements are only in regards to being published immediately without review by GitHub

I believe [the above] is correct, that bit is only stating about when actions are published immediately + automatically. You can have multiple actions in one repo but then you just have to follow the instructions further down the doc about publishing them.

Maybe the sentence could be reworked to be clearer, or a follow up added after the list of requirements that says something like: "If the action does not meet these requirements, follow the instructions below to publish it"

Let us know your thoughts regarding these review responses, and if you would be open to adding the suggested follow up statement after the list of requirements 💛