Repository navigation
Conversation
dreyfus92
force-pushed
the
feat/baseline-target-locations
branch
from
October 16, 2026 21:27
f5eb5e6 to
1cb1f7b
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.
reports each usage at its own location instead of flagging the whole file, using the new ranges +
baselineStatusOf/yearOffrom baseline-detector. messages now name the feature, e.g.`promise-withresolvers` is Baseline 2024, above the 2023 floor.Note
stacked on the baseline-target rule draft, only the last commit is new. draft until there's a baseline-detector release with the ranges.