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
Describe the Housekeeping
As a part of the parent story, the workflows for Traction UI can be migrated to shared workflows and improved upon. One of the biggest improvements can be made to ci.yml because there is a lot of repetition when setting up environments for testing and linting.
Workflows to migrate
ci.yml - This consists of prettier, ESLint, vitest, and cypress. These individual actions should be migrated into shared workflows, and then pulled into the main CI action. This means that the same node instance can be used.
automated_release.yml - Use the shared workflow version of this, it's used everywhere.
asset_dispatch.yml - Creates and uploads releases. This is fairly similar to append_release.yml in other repos, it could be consolidated and made into one shared workflow?
Potential improvements
Setup any environments (node/bundle) an cache them. These cached instances can then be used, being relied on by each step, so that the instance is only created once.
Additional context
This repository already has some shared workflows, these can be left. There is also an action to generate documentation for Traction. This doesn't need to be migrated to a shared workflow, but there can be improvements made, including relying on the node setup from the other actions here.
The text was updated successfully, but these errors were encountered:
psd-issuerbot
changed the title
Migrate & Improve GitHub Actions - Traction UI
Y25-098 - Migrate & Improve GitHub Actions - Traction UI
Feb 6, 2025
Describe the Housekeeping
As a part of the parent story, the workflows for Traction UI can be migrated to shared workflows and improved upon. One of the biggest improvements can be made to
ci.yml
because there is a lot of repetition when setting up environments for testing and linting.Workflows to migrate
ci.yml
- This consists of prettier, ESLint, vitest, and cypress. These individual actions should be migrated into shared workflows, and then pulled into the main CI action. This means that the same node instance can be used.check_release_version.yml
- Use the shared workflow version of this, it's used everywhere.automated_release.yml
- Use the shared workflow version of this, it's used everywhere.asset_dispatch.yml
- Creates and uploads releases. This is fairly similar toappend_release.yml
in other repos, it could be consolidated and made into one shared workflow?Potential improvements
Setup any environments (node/bundle) an cache them. These cached instances can then be used, being relied on by each step, so that the instance is only created once.
Related issues
Additional context
This repository already has some shared workflows, these can be left. There is also an action to generate documentation for Traction. This doesn't need to be migrated to a shared workflow, but there can be improvements made, including relying on the node setup from the other actions here.
The text was updated successfully, but these errors were encountered: