A team has written a custom action and must decide between keeping it in a public repository, keeping it in a private repository, or publishing it to the GitHub Marketplace. They want it to appear in the Marketplace catalogue with search and category placement so the wider community can discover and adopt it. Which two conditions must hold before this Marketplace listing can be created? Select TWO.
- AThe repository holding the action must be public, because the GitHub Marketplace will only create a listing for an action whose source code is openly readable rather than kept in a private repository. Correct
- BThe repository must contain a single action defined by an action.yml or action.yaml file at its root, because the Marketplace lists exactly one action per repository identified by that root metadata file. Correct
- CThe repository must enable GitHub Pages on its default branch, because the Marketplace renders the listing's description page from the published Pages site rather than from the action's own metadata file.
- DThe repository must store the action inside a docker subdirectory, because the Marketplace only accepts container actions and expects the Dockerfile and metadata to live together beneath that folder.
Why A is correct: A Marketplace listing requires the action to live in a public repository, so a private repository cannot be listed and the source must be openly readable to be published.
Why B is correct: The Marketplace recognises one action per repository through a single action.yml or action.yaml at the root, so a missing or misplaced metadata file blocks the listing entirely.
Why C is wrong: Tempting because Pages publishes web content, but Marketplace listings draw from the release and metadata, so enabling Pages is irrelevant to creating a listing.
Why D is wrong: Tempting since container actions exist, but the Marketplace lists JavaScript, composite, and Docker actions alike, so no docker subdirectory layout is required.