-
Notifications
You must be signed in to change notification settings - Fork 370
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
Action is ignoring non-stale tag on issues. #1178
Comments
Hello @NotLazy 👋, |
I looked for changes in the file that uses Maybe it has something to do with the escaping of the exclamation mark? |
Tried without escaping and I'm getting errors now. |
Hi @NotLazy , We tried investigating issue with the provided details and tried the given workflow. We see that the workflow run fails with Invalid workflow file error with exempt-issue-labels: !stale . Please check the workflow run :- https://github.com/setup-actions-demo/stale-test/actions/runs/12158864953 for more details We suggest you to escape special character (!) with the help of single or double quotes in the workflow for the exempt-issue-label value, that should reolve the issue. You can refer the workflow run with the suggested solution on the following url :- https://github.com/setup-actions-demo/stale-test/actions/runs/12199078047/job/34032166470 |
I think this fixed it, thank you. |
Hi @NotLazy , Thank you for confirming and we will close this ticket, feel free to re-open this ticket incase of any queries or issue. |
Description: I've configured the stale action to not mark issues with the
!stale
label as stale, usingexempt-issue-labels: \!stale
which was working for some time when I added it 7 months ago, but for the last 3-4 months it's been ignoring the labelAction version: v5
Platform:
The runner is configured to use ubuntu-latest
Runner type:
Github runs the action automatically.
Repro steps: https://github.com/hainguyents13/mechvibes/blob/master/.github/workflows/stale.yml
Expected behavior: I expect the issues to not be marked as stale, as was previously working 6-7 months ago.
Actual behavior: Issues which should not be marked stale are being marked stale.
The text was updated successfully, but these errors were encountered: