feat: add --range flag for checking multiple commits in CI#29
Merged
Conversation
Without this, checking a range of commits in CI required a shell loop with manual exit code aggregation. --range origin/main..HEAD runs all checks across the range and exits non-zero if any commit fails. Signed-off-by: Nerijus Bendžiūnas <nerijus.bendziunas@gmail.com>
benner
force-pushed
the
feat/add-range-checking
branch
from
0f548df to
4e33bb5
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.
Without this, checking a range of commits in CI required a shell loop
with manual exit code aggregation. --range origin/main..HEAD runs all
checks across the range and exits non-zero if any commit fails.
NLTK data is loaded only after confirming the range is non-empty, so
an empty range returns immediately without paying the startup cost.