Where to Launch a GitHub Action: Marketplace Rules, Awesome Lists and Where Maintainers Look
Launch a GitHub Action by publishing it to GitHub Marketplace, which lists actions immediately and does not review them as long as the action sits in a public repository with a single action.yml at the root and a unique name. You accept the Marketplace Developer Agreement, have two-factor authentication on, and tick a box when you draft a release. Then tell maintainers through a curated list, a technical post and Show HN.
What does GitHub Marketplace require before it lists an action?
Unlike most stores on this site, this one has no reviewer. GitHub’s documentation, read on 13 November 2026, says actions are published to the Marketplace immediately and are not reviewed, provided they meet a short list of conditions. That makes it the fastest route to a public listing in this whole category, and the one where the quality bar is only what you set.
| Condition | In practice |
|---|---|
| Public repository | The action’s source is open to read; no private listings |
| One action.yml or action.yaml at the root | Other metadata files in sub-folders are not listed automatically |
| A unique name in the metadata | It cannot match an existing action, a Marketplace category or a GitHub feature name |
| Not another account’s name | Names matching a user or organisation belong to that owner |
| Developer Agreement accepted | The Publish checkbox stays disabled until the repository owner accepts it |
| Two-factor authentication | Publishing a release requires it |
To publish, open the metadata file in your repository, follow the banner to draft a release, choose to publish the action to the Marketplace, pick a primary category, write a version tag and title, and publish the release. Each later tagged release can be published to the same listing. If you delete the repository, the listing is deleted too and the name becomes available to others.
Where do people discover a new action?
People find actions three ways: by searching the Marketplace, by copying a line from a repository they admire and by reading a recommendation. The places below cover each.
01 GitHub Marketplace
GitHub’s own catalogue, with a page for each published action, linked to its repository and releases.
- Review
- None; actions are published immediately when they meet the requirements
- Cost
- No fee is named on the publishing page for actions
- Badge
- A verified creator badge exists and is separate from the verified badge on an organisation’s profile
- Removal
- Untick publish on each published release to remove an action
The listing page shows your README and the release version, so the README is the product page. Put the smallest working workflow snippet at the top, then a table of inputs and outputs, then examples for the two most common setups.
Pick the primary category a user would browse, not the one you find flattering. A repository transfer keeps the listing, but the verified creator badge is lost unless the new owner is also verified.
02 Awesome Actions
A curated list of things related to GitHub Actions, grouped by purpose.
- Format
- A GitHub README with sections such as Utility, Static Analysis, Deployment and Notifications
- How to add
- Through its repository’s contributing process; read the guidelines there first
A curated list is useful because people browse a category there, not just search a name. Check that your action is not a duplicate of an existing entry, and say what yours does differently in one line.
We read the list’s README on 13 November 2026 but not its contributing rules in full, so follow its instructions at submission time.
03 Show HN
Hacker News’s section for things you made that other people can try.
- Fits when
- The action solves a problem developers recognise, such as slow builds or flaky releases
- Needs
- A reader can try it in a repository of their own within minutes
An action is easy to try, since the reader pastes a few lines into a workflow. Show the before and after of a real pipeline with timings you measured yourself.
A tiny wrapper around a single shell command will be treated as trivial. Say what the action handles that the raw command does not, such as caching, retries or clear error output.
04 Console (console.dev)
A free weekly newsletter that reviews developer tools and beta releases.
- Suggest
- Email the details, per its criteria page
- Questions it asks
- Whether the tool is for developers, easy to install, fast and well documented
Most single actions are too small to be reviewed as a tool, but an action that fronts a service or a larger open-source project can fit. Suggest the project, with the action as the way in.
It lists sponsors as clearly marked text ads and says it does not do sponsored reviews.
05 Post your build ideas (our board)
A free launch board with a developer tools category.
- Use
- A permanent page with the Marketplace link and a copyable workflow snippet in the description
- Limit
- A small, builder-heavy audience
Describe the pipeline job the action replaces, and paste the three-line usage. Anyone can comment without an account, so people can ask about a case you have not covered.
For related automation gaps others have named, browse the developer tool ideas.
What should you decide before the first release?
- The name. It must be unique across Marketplace actions and cannot collide with a category, a user or an organisation you do not own. Check it before you write the README around it.
- One action per repository. Keep the repository to the metadata file, code and files the action needs, so the release tags one tidy unit.
- The version tag. Users see it on the Marketplace page, so choose a scheme you will keep.
- The 2FA setup. Publishing needs it, so enable it a day ahead, not during the release.
The GitHub Action launch playbook has the dated steps, and the open source launch checklist covers repository hygiene. If your action wraps a command, the CLI tool guide explains how that command gets installed elsewhere.
Frequently asked questions
Does GitHub review actions before listing them?
No. GitHub’s publishing page says actions are published to Marketplace immediately and are not reviewed as long as they meet its requirements: a public repository, a single action.yml or action.yaml at the root and a unique name. You also have to accept the Marketplace Developer Agreement and use two-factor authentication when publishing the release.
How do I remove an action from the Marketplace?
Edit each release you published to the Marketplace and untick the option to publish it, then update the release. GitHub’s page says you must do this for every published release. Deleting the repository also deletes the listing, and the unique name identifier then becomes available for someone else to use.
Can my action have the same name as my GitHub username?
Yes, if you own that user or organisation account. GitHub’s rules say an action’s name cannot match a user or organisation unless its owner is the one publishing, and cannot match an existing action, a Marketplace category or a reserved GitHub feature name. Check the name before you build branding around it.
Post your build ideas publishes this page and runs a free launch board that competes with some of the sites it names. Facts about other sites came from their own pages on the date shown above; terms, queues and prices change, so confirm on their sites before you decide. About the publisher.