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
GithubRunner has been updated to work with the new workflows included in examples. This requires use of the schema_map.json file and having the workflows use the schema names, rather than JSON encoded schemas. This ensures that any schema run by the bot is present in the repo. Replace existing workflows with new workflows in examples/workflows.
Updated migration commands.
atmigrate-1.0.1 to migrate Manager for 1.0.1 changes.
atmigrate-1.0.3 to migrate Scheduler/Schema Map for 1.0.3 changes.
Documentation
Added documentation for creating and using custom components, including an example PR.
New Components
Added ExtraDataBatcher that allows batching items using the extra_data field of the items.
Added FileRegexBatcher that allows using regexes against file contents to produces batches with metadata.
Features
Added a max_submissions option to schema configs and scheduling to allow slower rollouts for changes that can prevent overwhelming code review.
Update Change to have get_schema_name() that is used for Condition. This allows GithubChange to pull schema name from the branch.
Add a schema_map.json file and some associated functionality to run command so that workflows can be moved to rely on information in the repo when determining schemas and no longer pass JSON encoded schemas around.
Make run github workflow use the schema name.
Added in/not in comparisons.
Fixes
Fix workflows to checkout the repo as the supplied bot, rather than as github-actions bot. This should prevent issues involving branch protection rules and force-pushes appearing under the wrong name.