Repository navigation
Stale label not being removed after new activity #441
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Describe your issue
The stale label isn't being removed from PRs when there's new activity even though remove-stale-when-updated isn't set.
Your stale action configuration
on:
push:
paths:
- .github/workflows/triage-issues.yml
schedule:
# Once every day at midnight UTC
- cron: "0 0 * * *"
issue_comment:
jobs:
stale:
if: >
startsWith(github.repository, 'Homebrew/') && (
github.event_name != 'issue_comment' || (
contains(github.event.issue.labels.*.name, 'stale') ||
contains(github.event.pull_request.labels.*.name, 'stale')
)
)
runs-on: ubuntu-latest
steps:
- name: Mark/Close Stale Issues and Pull Requests
uses: actions/stale@v3
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
days-before-stale: 21
days-before-close: 7
stale-issue-message: >
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs.
stale-pr-message: >
This pull request has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs.
exempt-issue-labels: "gsoc-outreachy,help wanted,in progress"
exempt-pr-labels: "gsoc-outreachy,help wanted,in progress"Further context
I made a comment on Homebrew/brew#11140 (comment) that should have caused the action to remove the stale label. The action did run successfully (the logs are available here). Here are the relevant lines from the logs:
[#11140] Found this pull request last updated 2021-05-08T15:44:35Z
[#11140] The option "onlyLabels" was not specified. Continuing the process for this pull request
[#11140] Days before pull request stale: 21
[#11140] The pull request is not closed nor locked. Trying to remove the close label...
[#11140] There is no close label on this pull request. Skip
[#11140] This pull request has a stale label
[#11140] This pull request has no assignee
[#11140] Skip the assignees checks
[#11140] Found a stale pull request
[#11140] Checking for label on pull request
[#11140] Pull request marked stale on: 2021-05-08T15:44:35Z
[#11140] Checking for comments on pull request since 2021-05-08T15:44:35Z
[#11140] Comments not made by actor or another bot: 0
[#11140] Pull request has been commented on: false
[#11140] Days before pull request close: 7
[#11140] Pull request has been updated: true
[#11140] Stale pull request is not old enough to close yet (hasComments? false, hasUpdate? true)
The line that says Pull request marked stale on: 2021-05-08T15:44:35Z seems to be incorrect, as the stale label was added 16 hours ago before that time. I wonder if the action is using the time of the latest comment as the time that the stale label was added.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Activity
Rylan12 commentedon May 8, 2021
This line looks like it explains the output that I'm seeing:
stale/src/classes/issues-processor.ts
Lines 483 to 484 in a61d498
To me, this means that
getLabelCreationDateisn't working properly because it seems to be returning a falsey value. I'm not sure what's going on here exactly. I simulated running thegetLabelCreationDatelocally and it seemed to return the correct value which makes me think that this query might not be working as expected:stale/src/classes/issues-processor.ts
Lines 452 to 457 in a61d498
Rylan12 commentedon May 9, 2021
One more thing to add, a colleague pointed out to me that the label is removed as expected during a scheduled run (we have it run every 24 hours). It seems that the times where it doesn't work are on
issue_commentevents. The reason we run onissue_commentevents is so the label can be immediately removed without needing to wait up to 24 hours. I guess we could run the job more frequently but even that wouldn't be as immediate as we'd like, I think.MAGICCC commentedon Jun 2, 2021
@Rylan12 I am thinking about using
issue_commentto trigger the workflow after a comment has been made in an issue/pr to remove the label, but I suppose this doesnt work yet right?Rylan12 commentedon Jun 3, 2021
I haven't seen a change since I've opened this issue, so I'd say don't bother with it at the moment. There are several downsides to having this (seemingly) useless
issue_commentrun, the biggest being that I get a notification every time that I comment on a non-stale issue or PR telling me that the run was skipped.But if you try and it works for you I'd love to see the configuration to try to figure out if I'm just doing something wrong 😅
I'm probably going to remove the
issue_commentevent from Homebrew's stale action configuration because it seems like it's totally useless. I don't have the time or the will to work on a PR to fix this, but I'm going to leave the issue open until it's auto-closed unless in case someone wants to work on it (I will be very grateful to that person)T6751 commentedon Jun 3, 2021
I think, this PR can fix this problem with
issue_comment#390MAGICCC commentedon Jun 5, 2021
This would be great to get this merged!
feat(options): add new options to avoid stale based on comments
feat(options): add new options to avoid stale based on comments
feat(options): add new options to avoid stale based on comments
feat(options): add new options to avoid stale based on comments
Rylan12 commentedon Jun 14, 2021
Thanks for working on this, @C0ZEN! ✨🎉
Did a quick test with this and it looks like it will fix our issue. Once this is released and we start using it I'll follow up if things still aren't working.
C0ZEN commentedon Jun 14, 2021
@Rylan12 sure, thanks for the feedbacks and I hope it's working as expected.
MAGICCC commentedon Jun 14, 2021
Hi @C0ZEN
I tested it on a testrepo for me but somehow it doesnt work as expected, I guess.
The issue was already old enough for being stale but the workflow didnt start yet. After a comment on issue https://github.com/MAGICCC/teststale/issues/3 the workflow triggered and added a comment on https://github.com/MAGICCC/teststale/issues/4 + https://github.com/MAGICCC/teststale/issues/5 and added stale label + removed it again.
Maybe I did something wrong...
2 remaining items
C0ZEN commentedon Jun 15, 2021
@Rylan12 "I hope it's working as expected."... The only time I say this and bingo a bug is introduced...
C0ZEN commentedon Jun 15, 2021
This one should be reopened then, due to the revert.
feat(options): add new options to avoid stale based on comments
C0ZEN commentedon Jun 24, 2021
@luketomlinson could you reopen please?
C0ZEN commentedon Jun 24, 2021
Seems same as #509
feat(options): add new options to avoid stale based on comments
Chriscbr commentedon Jul 8, 2021
Are there any suggested workarounds for this? We were running into this as well (here is an issue where the comment is ignored: projen/projen#723 and here is how the GitHub action was set up: https://github.com/projen/projen/blob/139d9e3fb66dffdcc976c5a6e873c98099258fcf/.github/workflows/stale.yml )
Rylan12 commentedon Jul 13, 2021
Thanks, @luketomlinson and @C0ZEN!
Did a quick test using the
mainbranch and it seems to fix our problem! 🎉 (hopefully for real this time)MAGICCC commentedon Jul 13, 2021
Indeed, tested it with my testrepo and its look fine! Thanks you. I am looking forward for v4 now :)
C0ZEN commentedon Jul 13, 2021
@luketomlinson well done
feat(options): add new options to avoid stale based on comments
marcomarsala commentedon Oct 28, 2022
not fixed. Just commented selectize/selectize.js#1824 and stale label not removed
feat(options): add new options to avoid stale base on comments (actio…