The Codeball action is now split into multiple smaller parts, opening up for a lot of flexibility and custom use cases.
- Added "status" sub-action
- Added "labeler" sub-action
- Changed "approver" sub-action to only approve PRs (removed features includes polling for the job result, and adding/creating labels).
New possibilities
- Add labels for non-approved contributions (see README for an example)
- Only run Codeball for files of a specific service has changed (see README for an example)
- Only run Codeball for a list of users, only on Mondays, or only for Go code... (anything that is possible to express in GitHub Actions should now be possible). Use it in the best that best helps your organization! 🚀
Breaking changes (from v1)
If you're using "v1" with the default options, you can switch to "v2" without any changes in behaviour.
Users of sturdy-dev/codeball-actions/approver@v1 with customisations are the only users that will see breaking changes. See the README.md for examples of to setup the old workflow with the v2 workflows.
Full Changelog: v1.2.0...v2.0.0