Add persistent Scopey enable and disable commands - #38
Merged
Conversation
calvin-archastro
force-pushed
the
feat/enable-disable-commands
branch
from
August 12, 2026 21:23
a239c63 to
3281443
Compare
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.
Summary
scopey disableandscopey enableenabledflag in the effective config while preserving existing settings and commentsVerification
cargo fmt --all -- --checkcargo test --locked --all-targets --all-featurescargo clippy --locked --all-targets --all-features -- -D warningsRUSTDOCFLAGS="-D warnings" cargo doc --locked --no-deps --all-features135 tests passed; 5 local-auth E2E tests remain intentionally ignored.