Prerequisites
Install Method
Other (repository GitHub Actions workflow)
Operating System
Other
Steps to Reproduce
- Open or edit an issue whose description passes the issue-description check so it receives the
ready for review label.
- Close the issue.
- Observe that the issue remains labelled
ready for review even though it is no longer awaiting review.
- Edit the closed issue and observe that the existing
edited trigger can validate it again without any closed-state guard.
Expected Behaviour
Closing an issue removes ready for review. If a closed issue is edited later, the label stays removed. Reopening the issue runs the existing validation flow and restores either ready for review or needs more info from the current description.
Actual Behaviour
The issue-description workflow listens only for opened, edited, and reopened, so closure does not remove ready for review. The checker also has no closed-state guard, allowing a later edit to a closed issue to apply the normal open-issue label result.
Logs / Screenshots
N/A - the stale label is visible on the closed issue and no application runtime is involved.
Model / Backend (if relevant)
N/A
Are you willing to submit a fix?
Yes - I can open a PR
Additional Information
The focused fix is to add closed to the existing workflow trigger and make the existing checker remove only ready for review before returning for any closed issue. Removing needs more info on closure is a separate policy choice and is not part of this report.
#2453 and PR #5486 are related maintenance work because they extract shared helpers from the same description-check scripts, but they intentionally preserve existing behavior and do not own this label lifecycle bug.
Prerequisites
devbranch and the bug is still present.Install Method
Other (repository GitHub Actions workflow)
Operating System
Other
Steps to Reproduce
ready for reviewlabel.ready for revieweven though it is no longer awaiting review.editedtrigger can validate it again without any closed-state guard.Expected Behaviour
Closing an issue removes
ready for review. If a closed issue is edited later, the label stays removed. Reopening the issue runs the existing validation flow and restores eitherready for revieworneeds more infofrom the current description.Actual Behaviour
The issue-description workflow listens only for
opened,edited, andreopened, so closure does not removeready for review. The checker also has no closed-state guard, allowing a later edit to a closed issue to apply the normal open-issue label result.Logs / Screenshots
N/A - the stale label is visible on the closed issue and no application runtime is involved.
Model / Backend (if relevant)
N/A
Are you willing to submit a fix?
Yes - I can open a PR
Additional Information
The focused fix is to add
closedto the existing workflow trigger and make the existing checker remove onlyready for reviewbefore returning for any closed issue. Removingneeds more infoon closure is a separate policy choice and is not part of this report.#2453 and PR #5486 are related maintenance work because they extract shared helpers from the same description-check scripts, but they intentionally preserve existing behavior and do not own this label lifecycle bug.