Normalize repository profile lookup#27
Merged
steipete merged 2 commits intoopenclaw:mainfrom May 2, 2026
Merged
Conversation
Co-Authored-By: Teddy CML <xthunder0@users.noreply.github.com>
Co-authored-by: Teddy CML <xthunder0@users.noreply.github.com>
steipete
force-pushed
the
codex/profile-lookup-normalization-fork
branch
from
3a6fd71 to
01c6097
Compare
Contributor
|
Landed via temp rebase onto main. Thanks @xthunder0! |
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
3 participants
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
targetRepoduringrepositoryProfileFor()lookup so mixed-case profile entries match normalized input.Context
This routes the downstream stop-gap from cloverthe-ai/clover-sweeper#16 upstream for cloverthe-ai/clover-sweeper#15. The latent bug is that lookup normalized only the caller input, then compared it against raw
candidate.targetRepo, so a mixed-case profile entry could fail to match itself and produce an unsupported-repo error that listed the same repo as known.Once this lands upstream, the downstream patch can be retired on the next clover-sweeper re-vendor cycle.
Verification
pnpm run build && node --test test/repository-profiles.test.tspnpm run checkNote: both checks ran on this machine with Node v22.22.1, which emits the repo's existing
>=24engine warning. No live sweep/apply/close commands were run.