GRI-1909: decide the specificity rule for overlapping schedule rules #204
Member
No description provided.
voidgazer
added 1 commit 2026-11-14 22:53:12 +00:00
Some checks failed
CI / cargo fmt (pull_request) Successful in 8s
Details
CI / the pre-push hook (pull_request) Successful in 9s
Details
CI / cargo clippy (pull_request) Successful in 1m27s
Details
CI / cargo test (pull_request) Successful in 1m27s
Details
CI / cargo deny advisories (pull_request) Failing after 1m22s
Details
CI / cargo deny (pull_request) Successful in 1m24s
Details
CI / repository boundary (pull_request) Successful in 8s
Details
CI / frontend-web (pull_request) Successful in 47s
Details
CI / Notify gate failed (pull_request) Has been skipped
Details
CI / CI (pull_request) Successful in 4s
Details
voidgazer
added 1 commit 2026-11-14 22:58:14 +00:00
Some checks failed
CI / cargo fmt (pull_request) Successful in 9s
Details
CI / the pre-push hook (pull_request) Successful in 10s
Details
CI / cargo deny advisories (pull_request) Failing after 1m51s
Details
CI / cargo deny (pull_request) Successful in 1m59s
Details
CI / cargo clippy (pull_request) Successful in 2m10s
Details
CI / cargo test (pull_request) Failing after 2m38s
Details
CI / repository boundary (pull_request) Successful in 32s
Details
CI / frontend-web (pull_request) Successful in 1m34s
Details
CI / CI (pull_request) Failing after 19s
Details
CI / Notify gate failed (pull_request) Successful in 22s
Details
voidgazer
added 2 commits 2026-11-15 01:38:06 +00:00
All checks were successful
CI / cargo fmt (pull_request) Successful in 8s
Details
CI / the pre-push hook (pull_request) Successful in 9s
Details
CI / cargo deny advisories (pull_request) Successful in 1m32s
Details
CI / cargo deny (pull_request) Successful in 1m32s
Details
CI / cargo clippy (pull_request) Successful in 2m12s
Details
CI / repository boundary (pull_request) Successful in 42s
Details
CI / frontend-web (pull_request) Successful in 1m35s
Details
CI / cargo test (pull_request) Successful in 3m25s
Details
CI / Notify gate failed (pull_request) Has been skipped
Details
CI / CI (pull_request) Successful in 3s
Details
Merge pull request 'GRI-1909: decide the specificity rule for overlapping schedule rules' (#204) from feature/GRI-1909-schedule-overlap into dev
No reviewers
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage!204
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/GRI-1909-schedule-overlap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?