Publishing an action in the GitHub Marketplace
Note: GitHub Actions is currently available in public beta, which means you should avoid using it for high-value workflows and content during this beta period.
Features and requirements may change at any time during this period. You can request to join the public beta on the GitHub Actions page. If you're participating in the beta, please contact support if you have any questions.
You can add the action you've created to the GitHub Marketplace by tagging it as a new release and publishing it.
Publishing an action to the GitHub Marketplace requires that the action lives in your public repository's root directory and it exists alone in that repository without other actions. To learn more about building GitHub Actions, see "Creating GitHub Actions."
Anyone can publish an action in GitHub Marketplace as long as they meet the terms of service. Unlike apps, GitHub Actions listed in GitHub Marketplace are not verified by GitHub.
To publish an action:
Create an action in your repository. To learn how to do this, see "Creating a new GitHub Action."
Note: GitHub requires that all LABELs in your Docker file are present if you want to publish your action to the GitHub Marketplace.
From your repository, click the Code tab and then the release tab.
- Click Draft a new release.
- Select Publish this action to the GitHub Marketplace.
- If the LABELs in your Dockerfile contain any problems, you will see an error message.
- If you see any on-screen suggestions, address them by updating your Docker file. Once complete, you will see an "Everything looks good!" message.
- Choose a "Primary Category" and, optionally, "Another Category" which will help people find your action in the GitHub Marketplace.
- Tag your Action with a version, and add a release title. This helps people know when a new version is available for them to use, and the name of that release. People will see the version in the Action's dedicated GitHub Marketplace page.
- Complete all other fields and click Publish release. Publishing requires you to use two-factor authentication. For more information, see "Configuring two-factor authentication" in the GitHub Help documentation.