Skip to content

Navigation Menu

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.

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

EVerest / everest-core Public

Notifications You must be signed in to change notification settings
Fork 86
Star 113

Code
Issues 36
Pull requests 33
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Security
Insights

Fix forced unlocking#542

Merged

corneliusclaussen merged 3 commits intomainEVerest/everest-core:mainfrom bugfix/fix-force-unlockEVerest/everest-core:bugfix/fix-force-unlockCopy head branch name to clipboard

Feb 14, 2024

+26-6

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Feb 14, 2024

Fix forced unlocking
corneliusclaussen
committed
Allow force unlock in state C as long as relais are open
corneliusclaussen
committed
Only allow force_unlock commands in states B and C
corneliusclaussen
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.