When creating and managing custom actions in an enterprise setting, which of the following is considered a best practice?

The correct answer is A. creating a separate repository for each action so that the version can be managed independently. Creating a separate repository for each custom action allows you to manage the versioning independently for each action. This approach provides flexibility, as each action can be updated, tested, and versioned separately, avoiding potential conflicts or dependencies between diffe

Manage GitHub Actions for the enterprise

Question

Options

Acreating a separate repository for each action so that the version can be managed independently
Bcreating a separate branch in application repositories that only contains the actions
Ccreating a single repository for all custom actions so that the versions for each action are all the
Dincluding custom actions that other teams need to reference in the same repository as application

How the community answered

(41 responses)

A
76% (31)
B
7% (3)
C
15% (6)
D
2% (1)

Explanation

Creating a separate repository for each custom action allows you to manage the versioning independently for each action. This approach provides flexibility, as each action can be updated, tested, and versioned separately, avoiding potential conflicts or dependencies between different

Topics

#custom actions#enterprise best practices#action versioning#repository management

Community Discussion

No community discussion yet for this question.

Full GITHUB-ACTIONS Practice