Closed
Description
Summary
GitHub provides linting for Actions in the editor console only. We could automate linting as a pre-commit hook and/or an action to validate workflows: https://github.com/rhysd/actionlint
In the first attempt there were some false positives due to shellcheck integration but may be easy to disable as we move most of our logic to Github-script.
Why is this needed?
We've had several issues with GitHub Actions in the past week due to bad syntax or using an unsupported syntax in blocks of a workflow - this could've caught early.
Which area does this relate to?
Automation
Solution
No response
Acknowledgment
- This request meets Lambda Powertools Tenets
- Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript