docs: clarify fetch vs classify date windows#51
Merged
Conversation
- Rename --start/--end option descriptions from "classification window" to "statistics baseline window" to make their purpose unambiguous - Expand the window section to explain that PRs *after* --end are the ones evaluated, not the ones in the baseline - Add a combined diagram showing how fetch and classify date ranges must relate to each other - Add an explicit warning that the fetch window must extend beyond the classify --end date or there will be no PRs to evaluate - Fix the end-to-end example which mistakenly used the same end date for both fetch and classify (leaving nothing to report) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Summary
--start/--endoption descriptions from "classification window" to "statistics baseline window" — the old label was ambiguous since the evaluation period is also part of classifying--endare what get evaluated and reported, not the ones inside the baselinefetchdate range must span both the baseline period and the post---endevaluation period--enddate, there will be no PRs left to reportfetchandclassify(e.g.--collate-end 2024-12-31paired with--end 2024-12-31), which would leave nothing to evaluateTest plan
🤖 Generated with Claude Code