Zigbee Lock: Force Migration Revert on Init - #3159
Open
hcarter-775 wants to merge 2 commits into
Open
Conversation
hcarter-775
requested review from
NoahCornell,
cjswedes,
ctowns,
gharveymn and
z-michel
July 31, 2026 17:55
|
Invitation URL: |
|
zigbee-lock_coverage.xml
Minimum allowed coverage is Generated by 🐒 cobertura-action against a3ee1e2 |
Test Results 73 files 540 suites 0s ⏱️ Results for commit a3ee1e2. |
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
1 participant
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.
Force Migration revert on init, given lock codes is accessible and a migration has already occurred.
Test added to prove out the migration reversion logic, and that code setting works as expected afterwards.