Repository navigation
Exclude posted activity from subsequent newsletter windows - #5
Merged
Merged
Conversation
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.
An early manual post previously left the scheduled collection window unchanged, allowing old activity to be presented again. Manual and scheduled collection now start after the latest posted activity cutoff, independently of the scheduler cursor. Published history still provides context for genuinely new follow-ups. The cutoff uses the collected window end so approval delays do not hide uncollected work, and persists across restarts and pruning with legacy posted-edition fallback. Stale overlapping pending drafts cannot be approved, and fully covered windows are declined before collection. No configuration changes or live bot restart are included. Validation: 97 offline tests / 432 assertions, formatting and diff checks pass. Regression tests cover early posts, follow-ups, restart/pruning, out-of-order publication, pending/rejected state, and stale approval without Discord access.