fix(lint): honor the --since flag when checking for version increment #508
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.
What this PR does / why we need it:
With the current implementation
ct lint
does not use the existing--since
flag when checking for a version increment.This is problematic when you want to use
ct lint
to validate the difference between the checked out commit and a previous commit on the same branch. Asct lint
tries to validate a difference between the current file andorigin/main
and these are the same files.It is also misleading to have a different way of handling the
--since
flag betweenlint
andlist-changed
.I changed the code to use the same logic as in
ct list-changed
to determine the base of the change when validating the version increment.Here are the verbose logs for before and after the change, we can see the difference in git commands issued:
Before
After