Improve recovery actions with extended-recover trigger#216
Merged
Conversation
dd9dca7 to
6f751c0
Compare
✅ Build ArtifactsVersion:
|
6f751c0 to
7cb9b51
Compare
✅ Build ArtifactsVersion:
|
Add troubleshooting documentation for "Klipper failed to start" error.
7cb9b51 to
b2d112d
Compare
✅ Build ArtifactsVersion:
|
✅ Build ArtifactsVersion:
|
This was referenced Feb 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reset actions now create /oem/.extended-recover to trigger extended config recovery on reboot. S49extended-config handles this file alongside the USB-based recovery.