feat: add --resolver subcommand to tack update#83
Open
peachey2k2 wants to merge 1 commit into
Open
Conversation
peachey2k2
force-pushed
the
resolver-subcommand-for-update
branch
from
July 8, 2026 07:56
920657d to
b0cd983
Compare
Contributor
|
this is what I suppose it could be argued the resolve is pin-related, but this also duplicates the codepath without including the vendored resolver detection + I can't say I'm particularly sold on it right now, if I were to merge this it'd probably be a strict alias of the existing command, and with the UpdateRequest stuff as its own commit. |
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
2 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.
update and refresh le' resolver