Repository navigation
fix(checkin): cover all accounts in one-click check-in - #543
Merged
Merged
Conversation
caigee-cmd
force-pushed
the
fix/checkin-all-coverage
branch
from
November 20, 2026 10:36
122e17a to
faace58
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
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.
One-click check-in now runs on the server across every eligible account, independent of browser filters, pagination, or client timezone parsing. It honors the disabled-account check-in setting and reports success, already, skipped, and error separately. Scheduled skipped attempts can retry in the existing 21:00 retry window. Validation: go build ./...; go test ./internal/app -run TestImportConstraints; targeted Go tests for accounts/control/console/runtime; worker plaintext tests 23/23; frontend npm run sync; git diff --check.