Create and publish actions lists "no workflow files" as a prerequisite.

[tommoor]

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/how-tos/create-and-publish-actions/publish-in-github-marketplace#prerequisites

What changes are you suggesting?

Removing the prerequisite as it is not true.

Additional information

No response

[pingaleganesh1234-debug]

Displaying verification statuses for all of your commits

You can enable vigilant mode for commit signature verification to mark all of your commits and tags with a signature verification status.

About vigilant mode

When you work locally on your computer, Git allows you to set the author of your changes and the identity of the committer. This, potentially, makes it difficult for other people to be confident that commits and tags you create were actually created by you. To help solve this problem you can sign your commits and tags. For more information, see Signing commits and Signing tags. GitHub marks signed commits and tags with a verification status.

By default commits and tags are marked "Verified" if they are signed with a GPG, SSH, or S/MIME key that was successfully verified. If a commit or tag has a signature that can't be verified by GitHub, we mark the commit or tag "Unverified." In all other cases no verification status is displayed.

However, you can give other users increased confidence in the identity attributed to your commits and tags by enabling vigilant mode in your GitHub settings. With vigilant mode enabled, all of your commits and tags are marked with one of three verification statuses:

Status	Description
Verified	The commit is signed, the signature was successfully verified, and the committer is the only author who has enabled vigilant mode.
Partially verified	The commit is signed, and the signature was successfully verified, but the commit has an author who: a) is not the committer and b) has enabled vigilant mode. In this case, the commit signature doesn't guarantee the consent of the author, so the commit is only partially verified.
Unverified	Any of the following is true: - The commit is signed but the signature could not be verified. - The commit is not signed and the committer has enabled vigilant mode. - The commit is not signed and an author has enabled vigilant mode.

You should only enable vigilant mode if you sign all of your commits and tags and use an email address that is verified for your GitHub account as your committer email address. After enabling this mode, any unsigned commits or tags that you generate locally and push to GitHub will be marked "Unverified."

You can check the verification status of your signed commits or tags on GitHub and view why your commit signatures might be unverified. For more information, see Checking your commit and tag signature verification status.

Enabling vigilant mode

1. In the upper-right corner of any page on GitHub, click your profile picture, then click Settings.
2. In the "Access" section of the sidebar, click SSH and GPG keys.
3. Under "Vigilant mode," select Flag unsigned commits as unverified.

[github-actions]

A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.

[tommoor]

This is a quick and easy documentation fix, the fact that it's been open for a month is somewhat telling.

[hesreallyhim]

I agree this is a confusing requirement. There examples in GitHub's own repos (e.g. https://github.com/actions/setup-node) that appear to contradict it. And even this GitHub docs page (https://docs.github.com/en/actions/how-tos/create-and-publish-actions/release-and-maintain-actions) appears to recommend the use of workflows for maintaining actions. The statement that it is enforced is also plainly false, at least on the natural reading. Thanks.

[yayaogsya]

Look I'm in need of some serious help I don't mind if you contact me privertly but I'll pay you very well if I can get a nerd to come sort all this drama out please

…

On Fri, 22 May 2026, 12:56 am Really Him, ***@***.***> wrote: *hesreallyhim* left a comment (github/docs#43228) <#43228 (comment)> I agree this is a confusing requirement. There examples in GitHub's own repos (e.g. https://github.com/actions/setup-node) that appear to contradict it. And even this GitHub docs page ( https://docs.github.com/en/actions/how-tos/create-and-publish-actions/release-and-maintain-actions) appears to recommend the use of workflows for maintaining actions. The statement that it is enforced is also plainly false, at least on the natural reading. Thanks. — Reply to this email directly, view it on GitHub <#43228 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B77B7ZTSO3WRKQWNFLKG6PL434KLHAVCNFSM6AAAAACWHGU4OCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKMBZGI4TENZTGI> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>