lock-threads
lock-threads copied to clipboard
dessant
GitHub Action that locks closed issues, pull requests and discussions after a period of inactivity
This may be something we are experiencing based on the git commit history size of our repo or the amount of activity during our lock window, but this action is...
I'd love to be able to utilize your (awesome!) lock-threads GitHub action in order to automatically lock the discussions in addition to issues and PR. Is something like that planned?...
This PR addresses #45 by introducing three new optional parameters: - `include-issue-currently-open` (default: `false`) - `include-pr-currently-open` (default: `false`) - `include-discussion-currently-open` (default: `false`) I do not _close_ discussions on my projects,...
Hey! I've given a try for discussions locking as introduced in #25 but from what I see, the action currently only closes discussions in state of `is:closed is:unlocked`, as stated...
Ref: https://github.com/dessant/lock-threads/issues/35 Myself and at least one other person (see issue above) are experiencing errors similar to: ``` Run dessant/lock-threads@v5 Request quota exhausted for request GET /search/issues Retrying after 60...
There's plenty of time still, but my output contains the following message: ``` [@octokit/request] "GET https://api.github.com/search/issues?q=repo%3Afirefly-iii%2Ffirefly-iii%20updated%3A%3C2025-02-19T02%3A26%3A13Z%20is%3Aclosed%20is%3Aunlocked%20is%3Aissue&sort=updated&order=desc&per_page=50" is deprecated. It is scheduled to be removed on Thu, 04 Sep 2025 00:00:00...
Hello, the `process-only` does not seem to work. I've tried using only `issues`, `prs` or `discussions` but the debug log shows issues, prs and discussions being processed regardless of what...
I have about 50 repos that all run this action at the same time. Seeing: > Error: You have exceeded a secondary rate limit. Please wait a few minutes before...
Update softprops/action-gh-release into release.yml fix node.js
