Update documentation link in manifest

[tinaboyce]

This PR will update the documentation link as the current one leads to a 404 error page. Was unsure whether I had to bump up the version as well in line 25.

Background:

While setting up HACS options, I clicked on the help icon and it lead me to this url https://hacs.xyz/docs/configuration/start, which displayed a 404 page.

Given a quick search on the repo had revealed this is the only place where the url was referenced, I thought to do a quick PR to update the documentation url.

[coderabbitai]

Walkthrough

Walkthrough

The pull request updates the manifest.json file for the custom_components/hacs module by changing the documentation URL. The new URL directs users to a page with practical usage instructions, replacing the previous link that focused on initial setup. No other fields in the manifest were altered, ensuring the overall functionality of the module remains unchanged.

Changes

File	Change Summary
custom_components/hacs/manifest.json	Updated documentation URL from https://hacs.xyz/docs/configuration/start to https://hacs.xyz/docs/use/.

Possibly related PRs

• Init ruff lint/format #3719: Changes focus on linting and formatting tools, unrelated to manifest.json.
• Only ship one frontend #3727: Modifications in frontend.py, not related to manifest.json.
• Remove compatibility with core without frontend.add_extra_js_url #3783: Similar to Only ship one frontend #3727, changes in frontend.py, unrelated to the main PR.
• Workaround deprecated http static path registration #3797: Involves changes to frontend.py, not connected to manifest.json.
• Add pre-release information to exported data #3841: Introduces a new prerelease attribute, unrelated to manifest.json.
• Use GraphQL to generate release content #3848: Focuses on prerelease attribute changes in base.py, not related to manifest.json.
• Use the same download handler for entity and websocket #3887: Changes in repositories/base.py, unrelated to manifest.json.
• Add handler to use raw URL for manifest.json in validation #3903: Introduces a new method for retrieving manifest.json, directly relevant to the main PR.
• Remove old sensor entity #3973: Removal of an old sensor entity, unrelated to manifest.json.
• Raise an error when update service target the downloaded version #3984: Adds version consistency checks in async_install, not related to manifest.json.
• Add workaround for bad filenames #3987: Introduces a workaround for bad filenames in plugin.py, not related to manifest.json.
• Show all pending updates #4024: Focuses on showing pending updates in the HACS UI, unrelated to manifest.json.

Tip

New features

Walkthrough comment now includes:

• Possibly related PRs: A list of potentially related PRs to help you recall past context.
• Suggested labels: CodeRabbit can now suggest labels by learning from your past PRs. You can also provide custom labeling instructions in the UI or configuration file.

Notes:

• Please share any feedback in the discussion post on our Discord.
• Possibly related PRs, automatic label suggestions based on past PRs, learnings, and possibly related issues require data opt-in (enabled by default).

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between b035707 and 7e98598.

Files selected for processing (1)

• custom_components/hacs/manifest.json (1 hunks)

Additional comments not posted (1)

custom_components/hacs/manifest.json (1)

19-19: Documentation URL updated successfully.

The change to the documentation URL is correctly implemented and aligns with the PR's objective to direct users to more relevant usage information.

---

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 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 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: 1

[ludeeus]

Thanks 👍