-
Notifications
You must be signed in to change notification settings - Fork 373
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
Last updated date appears to be incorrect #1184
Comments
I do see the |
Hello @michaelmior 👋, |
Yep, running into this with a bunch of stale PRs on my repo too. For some reason a bunch of them got unmarked as stale 3 days ago. (Appears this may be to do with the base branch getting force-pushed???) |
I am noticing this in our repos as well. Taking three example PRs for example, they each have a comment from the Stale Github action that they were quickly marked and unmarked as stale on 1/6/25. Neither PR has user activity on that day (they are automated dependabot type PRs), and all should be stale in that they are older than our configured threshhold for staleness. When I look in the Github action logs, I can see the action processed these PRs consecutively in the same batch, and they have very similar updated at messages: PR 1 -- |
Description:
As the excerpt from the log below shows, I have a pull request that is identified as having been updated within the past several days even though the last update I can see is nearly one year ago.
Action version:
v9
Platform:
Runner type:
Repro steps:
I am unsure how to reproduce this issue with a fresh repository, but here is an example of a run of this action that exhibits the problem.
For example, look at pull request 512.
It has not been updated in more than a year, but the action seems to think it was updated within the past several days.
Expected behavior:
The correct date of the last update should be identified.
Actual behavior:
The date of last update is not identified correctly.
The text was updated successfully, but these errors were encountered: