Repository navigation
Add evidence-backed workflow feedback and priority escalation - #490
Merged
Merged
Conversation
Signed-off-by: 澄潭 <zty98751@alibaba-inc.com>
Signed-off-by: 澄潭 <zty98751@alibaba-inc.com>
Signed-off-by: 澄潭 <zty98751@alibaba-inc.com>
Signed-off-by: 澄潭 <zty98751@alibaba-inc.com>
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
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.
Summary
issue-spec init. The built-in policy suggestspriority/highat three confirmed occurrences.feedback configurewhen the destination wants a custom threshold or automatic escalation. A threshold-only policy inherits the remaining defaults. The generated guidance offers feedback during authorized tasks, and projects can refine routing and publication rules inguidance.shared.Closes #472
Validation
initinstalled the guide and enabled the default path without a published policy. Preview and concurrent retries kept the count correct. The third event suggested promotion. A threshold-only policy suggested at two. An injected 403 on the GitHub label request preserved the comment, and a real authorized retry added the label on the same event.make test-fastand affected PostgreSQL, CLI and template tests passed. Workflow update preview was read-only and repeated generation produced zero changes.