A GitHub Action that automatically locks closed issues, pull requests, and discussions after a period of inactivity.
Lock Threads is a GitHub Action that automatically locks closed issues, pull requests, and discussions after they have been inactive for a specified period. It helps repository maintainers reduce clutter and prevent unnecessary engagement on resolved threads by automating a common moderation task. The action is highly configurable, allowing fine-grained control over which threads are locked and when.
Open-source maintainers, project administrators, and teams managing active GitHub repositories who need to keep discussion areas organized and focused. It's particularly useful for projects with high issue volumes or long-lived repositories.
Developers choose Lock Threads because it eliminates manual thread locking, saves maintenance time, and offers extensive customization through date filters, label-based rules, and commenting options. It's a reliable, community-tested action that integrates seamlessly into GitHub workflows.
GitHub Action that locks closed issues, pull requests and discussions after a period of inactivity
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Offers extensive filtering options by creation/closure dates, labels, and ISO 8601 time intervals, allowing precise targeting of threads to lock, as detailed in the input parameters list.
Supports adding customizable comments and modifying labels before locking, enhancing transparency and organization, with examples for issues, PRs, and discussions.
Handles issues, pull requests, and discussions individually or in combination via the process-only input, making it versatile for different repository needs.
Reduces manual maintenance by automatically locking threads after configurable inactivity periods, saving significant time for active project maintainers.
Only processes 50 threads per run to avoid GitHub abuse prevention mechanisms, which can delay cleanup in repositories with large backlogs, as admitted in the README.
With over 50 input parameters, setting up advanced rules can be daunting and error-prone, especially for users new to GitHub Actions or YAML workflows.
Relies on scheduled cron jobs or manual triggers, meaning threads may remain unlocked between runs, missing immediate action for recently inactive threads.