Skip to content

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Sign in

Sign up

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

Hypfer / Valetudo Public

Notifications You must be signed in to change notification settings
Fork 403
Star 7k

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Lock Threads

Lock Threads #1089

Sign in to view logs

Sign in to view logs

Lock Threads

Lock Threads #1089

Summary
Jobs
- lock_all_after_1y_of_inactivity
- lock_invalid_issues
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

1 warning

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

lock_all_after_1y_of_inactivity

succeeded Jan 3, 2025 in 5s

Loading

Re-running jobs...

You can’t perform that action at this time.