chore: add cron trigger to Feature Planner (every 30 min)#96
Merged
zacharias-ona merged 1 commit intomainfrom Apr 16, 2026
Merged
chore: add cron trigger to Feature Planner (every 30 min)#96zacharias-ona merged 1 commit intomainfrom
zacharias-ona merged 1 commit intomainfrom
Conversation
User-filed issues only get the bug/feature label from templates — they need the Feature Planner to triage and add status:backlog before the Bug Fixer or Feature Builder can pick them up. Without a cron trigger, issues sit in limbo until someone manually runs the planner. Co-authored-by: Ona <no-reply@ona.com>
zacharias-ona
added
the
ona-user
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
Author
|
✅ UI verification skipped — no UI files changed (no |
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.
User-filed issues only get the
bug/featurelabel from templates — they need the Feature Planner to triage and addstatus:backlogbefore the Bug Fixer or Feature Builder can pick them up. Without a cron trigger, issues sat in limbo until someone manually ran the planner.Adds a
*/30 * * * *cron trigger alongside the existing manual trigger.