Implement CLI front-end for loader-v4 commands #33289
Merged
Conversation
This file contains 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
pgarg66
force-pushed
the
loader-v4-cli-fe
branch
from
a9e33f0 to
34ef713
Compare
Codecov Report
@@ Coverage Diff @@
## master #33289 +/- ##
========================================
Coverage 81.9% 81.9%
========================================
Files 791 791
Lines 214749 215075 +326
========================================
+ Hits 176060 176334 +274
- Misses 38689 38741 +52 |
Lichtso
approved these changes
Sep 19, 2023
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.
Problem
We need a loader-v4 CLI command front-end for testing PRv2 until we have a cargo registry interface which speaks the cargo "sparse" protocol so that people can use
cargo publishdirectly.Summary of Changes
Add the CLI subcommands, description and integrate to the processors for loader-v4.
Fixes #