Decision: do the two named approvals before main apply here? (Q3) #30
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage#30
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
What
Open question Q3. Assumption today: no; green gates plus the product owner's review.
Done when
Answered, and
plan/open-questions.mdmoves Q3 to Answered.Plan
plan/open-questions.md#q3
Status
Product owner decision.
Routing/Hold: no agent is routed to this issue automatically. To take it yourself, assign yourself. Vivy removes the hold when it is handed to an agent.Created for GRI-1818 from
plan/overview/roadmap.mdand the MVP plan on GRI-1761.yes, for opening a PR to main. But I will merge it in to main.
Recorded in PR #72: two named approvals (CTO for tests, Security Checker) on the dev→main PR; you merge. The forge already requires 2 approvals on main. It does not restrict who may merge to main; I can set a merge whitelist with only you on it if you want that enforced.