Repository navigation
Fix exclusion policy and mobile dialog scrolling - #90
Merged
Merged
Conversation
ttlequals0
changed the title
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.
Compose shares startup settings across web/worker; the configuration guide adds a six-mount read-only example. Saved exclusions govern scans, scheduled scans, and selected-file rescans. Legacy JSON/environment rules import once, with existing database rows taking precedence.
EXCLUDED_EXTENSIONSnow applies across scanner paths. Mobile dialogs and the sidebar fit the visible browser height and keep background scrolling locked until the last overlay closes.Validation: 929 tests, frontend build, WebKit checks, CI, CodeQL, and rebuilt-image checks passed. Trivy reported 505 unchanged MEDIUM findings, no HIGH/CRITICAL issues, and no fixable findings. Deployed 2.10.4; live version, health, and exclusions endpoints returned HTTP 200, and deployed JS/CSS and image hashes matched.