Suppress missing description/repository/etc warnings when publishing to a custom registry
Open
Nobody has claimed this yet.
A-interacts-with-crates.io
A-registries
Command-publish
S-accepted
- Dominant language
- Rust
- Stars
- 15.5k
- Forks
- 3k
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 51
Description
These fields don't necessarily make as much sense if you're publishing to an internal registry where there isn't the same need for discoverability as there is on crates.io.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or an entry point. Start by reproducing a publish to a custom registry and locate the missing description, repository, and related warnings; done means those warnings are suppressed for custom registries while remaining available where discoverability metadata is expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100