Is there an existing issue that is already proposing this?
[X] I have searched the existing issues
Is your feature request related to a problem? Please describe it
Currently the only way to validate expected behavior is by running this action for a project. Given that most company projects are private, this creates challenges for sharing information on an initiative like this.
Describe the solution you'd like
By adding jest, we can write test cases for validating expected behavior.
Using CircleCI, we can add jobs to this project that run for each commit pushed. PRs can be configured to only allow merging if all checks in CircleCI pass.
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
Currently the only way to validate expected behavior is by running this action for a project. Given that most company projects are private, this creates challenges for sharing information on an initiative like this.
Describe the solution you'd like
By adding jest, we can write test cases for validating expected behavior.
Using CircleCI, we can add jobs to this project that run for each commit pushed. PRs can be configured to only allow merging if all checks in CircleCI pass.
Teachability, documentation, adoption, migration strategy
Increased reliability will inspire confidence in proposed features and released versions.
What is the motivation / use case for changing the behavior?
This will help reduce the risk of blocking defects making their way into a released version of the Action.