-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor GitHub Actions workflow for fixture regeneration #90
base: main
Are you sure you want to change the base?
Conversation
- Renamed job from `trigger_pipeline` to `regenerate_fixtures`. - Simplified the workflow by using an external action for fixture regeneration. - Removed redundant steps related to checkout, Go setup, and fixture update. - Inherited secrets for better security management.
Triggered a Github Actions job to update fixtures. |
Triggered a Github Actions job to update fixtures. |
Triggered a Github Actions job to update fixtures. |
Triggered a Github Actions job to update fixtures. |
Triggered a Github Actions job to update fixtures. |
Triggered a Github Actions job to update fixtures. |
CI runs are being triggered on pushes from github action. |
Triggered a Github Actions job to update fixtures. |
CI runs are being triggered on pushes from github action. |
This pull request refactors the GitHub Actions workflow for fixture regeneration. The
trigger_pipeline
job has been renamed toregenerate_fixtures
and the workflow has been simplified by using an external action for fixture regeneration. Redundant steps related to checkout, Go setup, and fixture update have been removed. Secrets are now inherited for better security management.