What are two reasons to keep an action in its own repository instead of bundling it with other application code? (Each correct answer presents a complete solution. Choose two.)

Question

Options

• AIt makes the action.yml file optional.
• BIt makes it easier for the GitHub community to discover the action.
• CIt widens the scope of the code base for developers fixing issues and extending the action.
• DIt decouples the action's versioning from the versioning of other application code.
• EIt allows sharing workflow secrets with other users.

• A
  3% (1)
• B
  95% (38)
• C
  3% (1)

Explanation

Keeping an action in a dedicated repository offers two key advantages. First (B), discoverability: GitHub Marketplace requires an action to be in a public repository to be listed there, making it easy for the broader GitHub community to find and use. Bundling an action inside an application repo buries it and prevents Marketplace publication. Second (D), independent versioning: when the action lives in its own repo, it can follow its own release cycle with semantic version tags (v1, v2, etc.) that consumers pin to. If bundled with application code, every unrelated application change risks bumping or confusing the action's version history. Option A is wrong - action.yml is always required. Option C is wrong - a narrower, dedicated codebase is actually easier, not harder, to maintain. Option E is wrong - repository isolation does not enable secret sharing.

No community discussion yet for this question.