fix: move option within cargo-dist config

[mistydemeo]

This places the display-name field within the main dist config.

Refs #458.

Summary by CodeRabbit

• New Features
  • Introduced a display-name configuration option for a custom application name in release notes and package listings.
• Improvements
  • Restructured display-name for better clarity and context within package metadata under [package.metadata.dist.bin-aliases].

[coderabbitai]

Walkthrough

Walkthrough

The recent changes introduce a new configuration option called display-name in the Cargo.toml file. This option allows for a custom display name for the application, enhancing the package's metadata for better clarity in contexts like release notes. The display-name entry was relocated under the [package.metadata.dist.bin-aliases] section, linking it to the alias marzano, which improves organization and usability without affecting the core functionality.

Changes

Files	Change Summary
crates/cli_bin/Cargo.toml	Introduced display-name for custom application naming; moved existing entry to [package.metadata.dist.bin-aliases] section.

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c8b3420 and 699dfe5.

Files selected for processing (1)

• crates/cli_bin/Cargo.toml (1 hunks)

Additional comments not posted (1)

crates/cli_bin/Cargo.toml (1)

70-71: Placement of display-name is appropriate.

The display-name configuration is logically placed within the [package.metadata.dist] section, aligning with its purpose related to distribution metadata.

Ensure that any documentation or tooling referencing display-name is updated accordingly to reflect this new location.

Verification successful

---

No additional references to display-name found.

The search indicates that the display-name is only present in the Cargo.toml file, with no other references in documentation or tooling needing updates. This confirms that the current placement and usage are correct.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify references to `display-name` in documentation or tooling.

# Test: Search for `display-name` usage. Expect: References to be updated to the new location.
rg --type toml --type md 'display-name'

Length of output: 87

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[mistydemeo]

Closing in favour of #459.