-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stale label not removed after receiving comments/commit #1132
Comments
Another example here open-telemetry/semantic-conventions#600 |
Hello @joaopgrassi |
Does the issue persist since you bumped the version? |
I have not seen it anymore, but it could be that I'm just not looking hard enough. I will try to keep an eye and see if anything gets closed unintentionally. |
I think I saw exactly the same issue in instaloader/instaloader#2172. I replied to prevent the bot from closing the issue, but it closed it nevertheless. |
Hi @joaopgrassi, We tried the provided workflow and investigated the issue, and we see that the label is getting removed after a comment by a non author on the same thread in the PR. We would recommend to add permission |
Hi @joaopgrassi , We are awaiting for your response, you can let us know if you have any queriers or the issue still exists. |
Description:
I recently enabled the stable bot PR here. Yesterday I noticed a PR that clearly had updates, but the
Stale
label is still not removed from the PR. I looked into the PR and here is the timeline:That is also consistent with what it is shown in the logs:
Action version:
2.312.0
Platform:
Runner type:
Repro steps:
Last job execution: https://github.com/open-telemetry/semantic-conventions/actions/runs/7750945678/job/21137993067
Affected PR: open-telemetry/semantic-conventions#627
Expected behavior:
The
Stale
label to be removed, since the PR received updates/activity:Actual behavior:
The
Stale
label is there.I'm not sure if I'm missing any configuration, but with the defaults it seems it should work:
The text was updated successfully, but these errors were encountered: