Repository navigation
chore(ocomment): adopt merged comment policies - #427
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.
Why
The development pin predates fixes for consecutive comment blocks, Biome suppressions, generic arrows in
.tsxfiles, and pinned Action annotations.The skill's version binding also has to match the selected checker.
Changes
Pin OComment to merged commit
552c8d0c340d25bc0557ba8988eaa231a67408d0and refresh only its lock entry.Update the existing skill compatibility record for the same revision.
Update both profile manifest sets for the deployed compatibility file's hash.
Validation
mise x -- just checkpassed.The locked development command selects the adopted revision and passes the embedded CLI self-test.
The native setup installed the same clean source revision on macOS, Linux, and Windows.
Each installed binary passed 640 embedded cases with no failures and reported two API-only cases outside the CLI.
The five tool inventory regressions passed after the compatibility update.
All 16 Windows manifests match the complete files generated on native Windows.
The 32 manifest changes contain only the compatibility file's hash.
Closes #421.
@coderabbitai ignore