Add issue management automations#4
Merged
Merged
Conversation
Remove pull_request_target trigger and simplify to issues-only workflow. Replace aws-actions/closed-issue-message with actions/github-script to avoid incompatible input requirements.
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
1 participant
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.
Issue Management Automations
Adds three GitHub Actions workflows for automated issue management:
Workflows Added
close-stale-issues.yml) — Closes issues after 7 days without reporter response (triggered byresponse-requestedlabel). Runs every 6 hours.closed-issue-message.yml) — Posts a standardized message on closed issues and locks the conversation.unlock-reopened-issue.yml) — Companion workflow that unlocks issues when reopened.issue-regression-labeler.yml) — Auto-appliesregressionandp1labels when a bug report indicates a regression.Labels Required
Before merging, create these labels in the repository:
response-requested(#fbca04) — Waiting for reporter to provide more informationclosing-soon(#e4e669) — Issue will be closed soon due to inactivityregression(#d93f0b) — Functionality that previously worked is now brokenp1(if not already present)Cross-Repo Coordination
This PR is part of a coordinated rollout across all
aws-durable-execution-*repositories.