forgejo: the label is the author's act, and flaky-mesh may squash again #36
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Ting/Jostoph!36
Loading…
Reference in a new issue
No description provided.
Delete branch "agent.teyla/Jostoph:tango/34-the-authors-label"
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?
The declaration half of #34, plus the one #33 repair Jostoph itself can declare.
Reviewed/Curated's description now says the AUTHOR sets it, per the owner's ruling of 2026-08-11: the author knows whether the line was curated, curation is a duty on every PR either way, and the label carries exactly one bit — the merge style. The comment above it records the error the old wording induced.larandar/flaky-meshjoins the estate declaration: measured with squash and merge-commits both off, it could not execute law 10's uncurated path at all. The fleetmergeStyles(declared, reconciled by the provider) reopen squash. Main-only, because no fastlane branch exists there and conformance should not create one as a side effect.The other two asks of #34 live outside this repository: org label
lar.ad#55 is being reworded on the forge directly, and flake-ops'pipeline_labelstranscription gets its own PR there.nix flake check'srepos-declare-what-must-holdandpolicy-matches-checkoutpass;nixfmtclean.Refs #33.
Closes #34.
91739c58b5to2ffea96939