You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the UEC DoS rewrite, we have amassed a pretty large catalogue of Github workflows and actions for various common tasks (code quality, linting, IaC operations, etc.)
After discussion with @stefaniuk, we deduced it may be worthwhile to try and fold these into the template somehow.
What is the feature that you are proposing to solve the problem?
The proposal is not necessarily to combine all of these workflows into the template repository per se (although some of the more lightweight actions might be quick wins), but perhaps to create something more like an internal marketplace of workflows and actions (each versioned in their own repository), which then may be consumed.
There may also be some overlap between this and the Coyote work that is ongoing.
What alternatives have you considered?
No response
Code of Conduct
I agree to follow this project's Code of Conduct
Sensitive Information Declaration
I confirm that neither PII/PID nor sensitive data are included in this form
The text was updated successfully, but these errors were encountered:
What is the problem this feature will solve?
As part of the UEC DoS rewrite, we have amassed a pretty large catalogue of Github workflows and actions for various common tasks (code quality, linting, IaC operations, etc.)
See https://github.com/NHSDigital/uec-dos-service-management/
After discussion with @stefaniuk, we deduced it may be worthwhile to try and fold these into the template somehow.
What is the feature that you are proposing to solve the problem?
The proposal is not necessarily to combine all of these workflows into the template repository per se (although some of the more lightweight actions might be quick wins), but perhaps to create something more like an internal marketplace of workflows and actions (each versioned in their own repository), which then may be consumed.
There may also be some overlap between this and the Coyote work that is ongoing.
What alternatives have you considered?
No response
Code of Conduct
Sensitive Information Declaration
The text was updated successfully, but these errors were encountered: