GH-200 · Question #37
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. The best practice for custom actions in an enterprise is (A): creating a separate repository for each action. This approach allows each action to be versioned independently using tags (e.g., v1, v2), makes it easy for other teams to reference a specific version using the…
Question
When creating and managing custom actions in an enterprise setting, which of the following is considered a best practice?
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
(33 responses)- A70% (23)
- B6% (2)
- C15% (5)
- D9% (3)
Explanation
The best practice for custom actions in an enterprise is (A): creating a separate repository for each action. This approach allows each action to be versioned independently using tags (e.g., v1, v2), makes it easy for other teams to reference a specific version using the standard 'owner/repo@version' syntax, isolates changes to one action from affecting others, and keeps the action's codebase focused and maintainable. (B) using branches in application repos mixes action code with application code and complicates versioning. (C) a monorepo for all actions makes independent versioning difficult. (D) embedding actions needed by other teams inside an application repository tightly couples unrelated concerns and makes cross-team reuse harder.
Topics
Community Discussion
No community discussion yet for this question.