Repository navigation
feat: scheduled_events tool and scheduling skill for the new drivers - #27
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 6 of the schedule work (framework v13.36).
scheduled_events: events with the driver that keeps each, placement against the configured driver (active / protected / fallback / to migrate), driver availability, late events, failures of the last week. Reads thecronoption and config only, so it answers on any 13.x.pollora-scheduling: fluent API, the three drivers,pollora:schedule:list|migrate|recover, replacement ofuse_laravel_scheduler.pollora:schedule:*commands and the tool.82 Pest tests, PHPStan, Rector, Pint. Tag with the framework's v13.36 release.