Remove server name in minecraft_server.markdown

[elmurato]

Remove "server name" during setup. Now only the "server address" is required.

Proposed change

Remove documentation of the configurable server name (previously entered during setup). Now it is obsolete and not required anymore. The user will only be asked for a server address while trying to add a new device. Refer to linked core PR for more information.

Type of change

• Spelling, grammar or other readability improvements (current branch).
• Adjusted missing or incorrect information in the current documentation (current branch).
• Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • I've opened up a PR to add logos and icons in Brands repository.
• Added documentation for a new feature I'm adding to Home Assistant (next branch).
• Removed stale or deprecated documentation.

Additional information

• Link to parent pull request in the codebase: Remove name in Minecraft Server config entry core#139113
• Link to parent pull request in the Brands repository: n.a.
• This PR fixes or closes issue: n.a.

Checklist

• This PR uses the correct branch, based on one of the following:
  • I made a change to the existing documentation and used the current branch.
  • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
• The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

• Documentation
  • Simplified Minecraft server setup instructions to require only the server address, removing the previously prompted server name and its default value.

[netlify]

✅ Deploy Preview for home-assistant-docs ready!

Name	Link
🔨 Latest commit	051cede
🔍 Latest deploy log	https://app.netlify.com/sites/home-assistant-docs/deploys/67bb2e868213750008c70541
😎 Deploy Preview	https://deploy-preview-37641--home-assistant-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

The Minecraft server integration documentation was updated to simplify the setup instructions. The changes remove the section that prompted users to enter the server name during setup, leaving only the prompt for the server address.

Changes

File	Change Summary
source/_integrations/minecraft_server.markdown	Removed the instructions prompting for the server name and default value details, now only requesting the server address.

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

source/_integrations/minecraft_server.markdown (1)

29-29: Punctuation Improvement Suggestion:
A static analysis hint suggests that a comma may be missing after the introductory phrase. Consider revising the line to:

During setup, you will be prompted to enter the **address** of the server.

This minor punctuation change could enhance readability.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~29-~29: A comma is probably missing here.
Context: ... integrations/config_flow.md %} During setup you will be prompted to enter the **add...

(MISSING_COMMA_AFTER_INTRODUCTORY_PHRASE)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 88603f6 and 051cede.

📒 Files selected for processing (1)

• source/_integrations/minecraft_server.markdown (1 hunks)

🧰 Additional context used

🪛 LanguageTool

source/_integrations/minecraft_server.markdown

[uncategorized] ~29-~29: A comma is probably missing here.
Context: ... integrations/config_flow.md %} During setup you will be prompted to enter the **add...

(MISSING_COMMA_AFTER_INTRODUCTORY_PHRASE)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Redirect rules - home-assistant-docs
• GitHub Check: Header rules - home-assistant-docs
• GitHub Check: Pages changed - home-assistant-docs

🔇 Additional comments (1)

source/_integrations/minecraft_server.markdown (1)

29-29: Simplified Setup Instructions:
The updated text now prompts users solely for the address of the server, which effectively removes the obsolete "server name" requirement. This change meets the PR objective of streamlining the setup process.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~29-~29: A comma is probably missing here.
Context: ... integrations/config_flow.md %} During setup you will be prompted to enter the **add...

(MISSING_COMMA_AFTER_INTRODUCTORY_PHRASE)

[c0ffeeca7]

Thank you, @elmurato 👍