Repository navigation
docs(notifications): document report behavior and scheduling - #2183
Draft
felipebergamin wants to merge 1 commit into
Draft
felipebergamin wants to merge 1 commit into
felipebergamin wants to merge 1 commit into
Conversation
Describe notification actions, subscriptions, recipient routing, storage, and cron jobs. Document CIP status-change gating and the current repeat-report flag behavior. Related: #2177 Assisted-by: OpenAI Codex Signed-off-by: Felipe Bergamin <[email protected]>
alanpeixinho
approved these changes
Oct 16, 2026
|
|
||
| | Action | Behavior | | ||
| | ------ | -------- | | ||
| | `new_issues` | Looks for recent issues, records newly discovered issue ID/version pairs, and emails a summary. Also generates individual reports for new Maestro build issues. | |
| `new_issues` searches a one-hour window, selects the highest recent version of | ||
| each issue, and excludes issues with older incidents. It compares the results | ||
| with the issue ID/version pairs already stored in SQLite before rendering the | ||
| summary. Test-linked issues enter this discovery path as boot issues. |
Contributor
There was a problem hiding this comment.
Can we ellaborate more on that? Why we have test-linked issues as boot-issues? Only boots (tests with boot path) should be boot issues.
|
|
||
| ### Hardware | ||
|
|
||
| Hardware subscription filenames must end in `_hardware.yaml` or `_hardware.yml`. |
Contributor
There was a problem hiding this comment.
this is not for this PR, but we could move the type of subscription to the yaml content, instead of having it as filename related.
This branch has not been deployed
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
2 participants
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.
The notification guide was missing supported actions and still described notification storage as JSON. Update it to match the current implementation, including checkout change detection, subscriptions, recipient routing, SQLite tracking, cron schedules, and email setup.
Validation
git diff --checkpassed. Documentation only; no application tests run.Reviewer instructions
docs/notifications.mdin GitHub's rendered view and follow its local links.backend/kernelCI_app/management/commands/notifications.pyand the schedule withbackend/kernelCI/settings.py.backend/:poetry run python manage.py notifications --action=fake_report. It should print a dry-run report without sending email.