docs(changelog): record the per-trigger effort scoping #82
No reviewers
Labels
No labels
already-shipped
bug
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
needs-decision
proposal
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: crenshawdev/cadence#82
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "cadence/changelog-64"
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?
#64 landed without a changelog entry.
Its report gave a reason that was true when it ran and had expired by the time it merged: the issue was milestoned v2.0.0 (I moved it to v1.5.0 mid-flight) and there was no
[Unreleased]section to file under (the worktree.baseRef work created one afterward).Worth announcing rather than leaving silent: on a stock install the
difftrigger now emits a visible line every fire when the configured effort differs fromcad-reviewer's pinnedhigh. Unannounced new output in a review run reads as a bug.Docs only. Blocks the v1.5.0 release notes being complete.
Refs #64