-
Notifications
You must be signed in to change notification settings - Fork 201
docs: update the help doc for oras manifest index create
#1650
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Overview
This PR updates the command usage for creating a manifest index to improve clarity on where the index is created and to ensure that positional arguments are ordered before flags.
- Updated the "Use" string in create.go to replace with and include
- Revised examples to reflect the new positional argument order and flag placement
Reviewed Changes
File | Description |
---|---|
cmd/oras/root/manifest/index/create.go | Updates usage string and examples for better clarity and command consistency |
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
cmd/oras/root/manifest/index/create.go:59
- [nitpick] Consider clarifying the separation between and in the usage string (e.g. by adding a delimiter) to enhance comprehension of the required positional arguments.
Use: "create [flags] <target>[:<tag[,<tag>][...]] <sources>[{<tag>|<digest>}...]"
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1650 +/- ##
==========================================
- Coverage 84.77% 84.74% -0.04%
==========================================
Files 126 126
Lines 5683 5683
==========================================
- Hits 4818 4816 -2
- Misses 615 617 +2
Partials 250 250 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
oras manifest index create
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work! Thanks for the contribution! LGTM
Let's merge this PR first and finish the remaining part in a separate PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but we will need another PR for oras manifest index update
1. Changing <name> to <target> explicitly states where the manifest index will be created. 2. Keeping all positional arguments first improves readability and reduces the risk of users mistaking flags like --oci-layout as having their own positional arguments. Fixes: oras-project#1638 Signed-off-by: Rohan Mishra <315scisyb2020rohanmishra@gmail.com>
…ect#1650) Signed-off-by: Rohan Mishra <315scisyb2020rohanmishra@gmail.com>
Fixes: #1638
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Please check the following list: