Skip to content

Improve Tankerkoenig docs #38662

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

Merged
merged 4 commits into from
Apr 22, 2025

Conversation

mib1185
Copy link
Contributor

@mib1185 mib1185 commented Apr 21, 2025

Proposed change

This improves the Tankerkoening docs by

  • restructuring the docs with proper sections
  • add configuration steps and integration options description
  • describe provided entities
  • add note about limitation of available fuel types
  • show usage examples
  • add troubleshooting hints
  • add remove instructions

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).
  • 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:
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue: fixes #

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
    • Expanded and restructured the documentation for the tankerkoenig integration.
    • Added detailed prerequisites, configuration options, and usage examples.
    • Introduced sections on data updates, provided entities, troubleshooting, and integration removal.
    • Clarified API usage limits and fuel type availability.

@mib1185 mib1185 requested a review from jpbede as a code owner April 21, 2025 18:24
@home-assistant home-assistant bot added the current This PR goes into the current branch label Apr 21, 2025
Copy link

netlify bot commented Apr 21, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 0ffe111
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/680733da5d31ac0008e81238
😎 Deploy Preview https://deploy-preview-38662--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

Copy link
Contributor

coderabbitai bot commented Apr 21, 2025

📝 Walkthrough

Walkthrough

The documentation for the tankerkoenig integration was extensively updated and reorganized. Additions include a new prerequisites section, expanded configuration instructions, explicit API key guidance, and a detailed explanation of configuration parameters. New sections cover data update intervals, entities provided by the integration, usage examples with YAML, troubleshooting steps, and instructions for removing the integration. The documentation now provides comprehensive guidance for setup, usage, and issue resolution, with updated recommendations on API usage limits and explicit notes about available fuel types.

Changes

File(s) Change Summary
source/_integrations/tankerkoenig.markdown Major expansion and restructuring of documentation: new sections for prerequisites, configuration, data updates, entities, usage examples, troubleshooting, and removal instructions; improved clarity and guidance throughout.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HomeAssistant
    participant TankerkoenigAPI

    User->>HomeAssistant: Initiate tankerkoenig integration setup
    HomeAssistant->>User: Request API key and configuration details
    User->>HomeAssistant: Provide API key, location, radius, etc.
    HomeAssistant->>TankerkoenigAPI: Fetch station data (every 30 minutes)
    TankerkoenigAPI-->>HomeAssistant: Return station and fuel price data
    HomeAssistant->>User: Create sensor and binary sensor entities per station
    User->>HomeAssistant: View/update fuel prices and station statuses
Loading

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (5)
source/_integrations/tankerkoenig.markdown (5)

25-25: Grammar: use correct verb form for setting up automations
“...and setup automations” should use the verb phrase “set up automations” (two words) to avoid confusion with the noun “setup.”


27-29: Typographical: add comma after introductory clause
In the sentence “To use this integration you need an API key…”, add a comma after “integration” for clarity:
To use this integration, you need an API key from tankerkoenig.

🧰 Tools
🪛 LanguageTool

[typographical] ~29-~29: It seems that a comma is missing.
Context: ...rmation. ## Prerequisites To use this integration you need an API key from tankerkoenig. ...

(IN_ORDER_TO_VB_COMMA)


33-33: Grammar: refine verb form in important note
Change “If you consider to define a custom polling interval” to “If you consider defining a custom polling interval” for more natural English.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~33-~33: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...e issued otherwise. If you consider to [define a custom polling interval](/common-task...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


38-49: Grammar: correct typos in configuration descriptions

  • “were to search” → “where to search”
  • “et during onboarding” → “set during onboarding”
    These small fixes will improve readability in the config parameter descriptions.

51-56: Reduce duplication in option flow configuration
You’ve repeated the “Stations” selection under the option flow. Consider consolidating or distinguishing these blocks:

  • Use a dedicated configuration_options macro for runtime options (instead of configuration_basic), or
  • Add a header clarifying this is for post‑setup options.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 75c797b and 764b065.

📒 Files selected for processing (1)
  • source/_integrations/tankerkoenig.markdown (1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/tankerkoenig.markdown

[typographical] ~29-~29: It seems that a comma is missing.
Context: ...rmation. ## Prerequisites To use this integration you need an API key from tankerkoenig. ...

(IN_ORDER_TO_VB_COMMA)


[uncategorized] ~33-~33: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...e issued otherwise. If you consider to [define a custom polling interval](/common-task...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


[grammar] ~63-~63: The singular determiner ‘this’ may not agree with the plural noun ‘integrations’. Did you mean “these”?
Context: ...ankerkoenig.de). ## Provides entities This integrations provides a set of {% term ...

(THIS_NNS)


[grammar] ~64-~64: Consider using the singular form after the singular determiner “This”.
Context: ...koenig.de). ## Provides entities This integrations provides a set of {% term "Binary senso...

(AGREEMENT_SENT_START)

⏰ 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 (2)
source/_integrations/tankerkoenig.markdown (2)

19-21: Validation of related documentation link
The newly added related section correctly points to the common‑tasks guide for defining a custom polling interval and uses a meaningful title. Ensure that the path /common-tasks/general/#defining-a-custom-polling-interval aligns with the actual URL structure in the docs.


36-36: Configuration flow include looks good
The inclusion of integrations/config_flow.md aligns with other integrations and clearly injects the setup flow instructions.

jpbede
jpbede previously approved these changes Apr 21, 2025
Copy link
Member

@jpbede jpbede left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thanks a lot 👍

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (5)
source/_integrations/tankerkoenig.markdown (5)

25-25: Use “set up” (verb) instead of “setup”
In this context “set up automations” (two words) is the correct verb form.

Suggested diff:

-The `tankerkoenig` integration allows you to monitor the fuel prices with [tankerkoenig.de](https://www.tankerkoenig.de/) from within Home Assistant and setup automations based on the information.
+The `tankerkoenig` integration allows you to monitor fuel prices via [tankerkoenig.de](https://www.tankerkoenig.de/) from within Home Assistant and set up automations based on that information.

29-29: Add missing comma for clarity
Insert a comma after “integration” to improve readability.

Suggested diff:

-To use this integration you need an API key from tankerkoenig.
+To use this integration, you need an API key from tankerkoenig.
🧰 Tools
🪛 LanguageTool

[typographical] ~29-~29: It seems that a comma is missing.
Context: ...rmation. ## Prerequisites To use this integration you need an API key from tankerkoenig. ...

(IN_ORDER_TO_VB_COMMA)


33-33: Use the gerund form “consider defining”
Replace “consider to define” with “consider defining” for correct English idiom.

Suggested diff:

-If you consider to [define a custom polling interval](/common-tasks/general/#defining-a-custom-polling-interval), then please keep in mind that requests should be limited to less than once every 5 minutes.
+If you consider defining a [custom polling interval](/common-tasks/general/#defining-a-custom-polling-interval), please keep in mind that requests should be limited to less than once every 5 minutes.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~33-~33: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...e issued otherwise. If you consider to [define a custom polling interval](/common-task...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


57-57: Correct typo “Weather” → “Whether”
Change to “Whether to show the station sensors on the map or not.”

Suggested diff:

-Show stations on map:
-    description: "Weather to show the station sensors on the map or not."
+Show stations on map:
+    description: "Whether to show the station sensors on the map or not."

66-66: Fix subject‑verb agreement
Change “This integrations provides” → “This integration provides”.

Suggested diff:

-This integrations provides a set of {% term "Binary sensor" %} and {% term Sensor %} entities for each selected gas station.
+This integration provides a set of {% term "Binary sensor" %} and {% term Sensor %} entities for each selected gas station.
🧰 Tools
🪛 LanguageTool

[grammar] ~66-~66: Consider using the singular form after the singular determiner “This”.
Context: ...koenig.de). ## Provides entities This integrations provides a set of {% term "Binary senso...

(AGREEMENT_SENT_START)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 764b065 and da30566.

📒 Files selected for processing (1)
  • source/_integrations/tankerkoenig.markdown (1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/tankerkoenig.markdown

[typographical] ~29-~29: It seems that a comma is missing.
Context: ...rmation. ## Prerequisites To use this integration you need an API key from tankerkoenig. ...

(IN_ORDER_TO_VB_COMMA)


[uncategorized] ~33-~33: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...e issued otherwise. If you consider to [define a custom polling interval](/common-task...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


[grammar] ~65-~65: The singular determiner ‘this’ may not agree with the plural noun ‘integrations’. Did you mean “these”?
Context: ...ankerkoenig.de). ## Provides entities This integrations provides a set of {% term ...

(THIS_NNS)


[grammar] ~66-~66: Consider using the singular form after the singular determiner “This”.
Context: ...koenig.de). ## Provides entities This integrations provides a set of {% term "Binary senso...

(AGREEMENT_SENT_START)

⏰ 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/tankerkoenig.markdown (1)

19-21: Front matter related entry looks good
The new related key is valid YAML and correctly links to the custom polling‑interval docs.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
source/_integrations/tankerkoenig.markdown (1)

44-44: Fix typo in location description
The word “et” should be “set” and casing of “Home” can be downcased. This duplicates an earlier suggestion.

- … defaults to the location of your Home which was et during …
+ … defaults to the location of your home which was set during …
🧹 Nitpick comments (4)
source/_integrations/tankerkoenig.markdown (4)

25-25: Refine introductory sentence grammar
Change “setup automations” (noun) to “set up automations” (verb) and consider dropping “the” before “fuel prices” for smoother flow.
Example:

- monitor the fuel prices … and setup automations
+ monitor fuel prices … and set up automations

29-29: Add missing comma after introductory clause
Insert a comma after “To use this integration” to correct the run‑on sentence.

- To use this integration you need an API key …
+ To use this integration, you need an API key …
🧰 Tools
🪛 LanguageTool

[typographical] ~29-~29: It seems that a comma is missing.
Context: ...rmation. ## Prerequisites To use this integration you need an API key from tankerkoenig. ...

(IN_ORDER_TO_VB_COMMA)


33-33: Use correct verb form
Replace “If you consider to define” with “If you consider defining” or “If you want to define” for proper English usage.

- If you consider to [define a custom polling interval]
+ If you consider defining [a custom polling interval]
🧰 Tools
🪛 LanguageTool

[uncategorized] ~33-~33: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...e issued otherwise. If you consider to [define a custom polling interval](/common-task...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


46-46: Standardize unit formatting
Recommend adding a space between the number and unit (2 km) for consistency with other docs.

- (_default: 2km_)
+ (_default: 2 km_)
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between da30566 and e5774f5.

📒 Files selected for processing (1)
  • source/_integrations/tankerkoenig.markdown (1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/tankerkoenig.markdown

[typographical] ~29-~29: It seems that a comma is missing.
Context: ...rmation. ## Prerequisites To use this integration you need an API key from tankerkoenig. ...

(IN_ORDER_TO_VB_COMMA)


[uncategorized] ~33-~33: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...e issued otherwise. If you consider to [define a custom polling interval](/common-task...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


[grammar] ~65-~65: The singular determiner ‘this’ may not agree with the plural noun ‘integrations’. Did you mean “these”?
Context: ...ankerkoenig.de). ## Provides entities This integrations provides a set of {% term ...

(THIS_NNS)


[grammar] ~66-~66: Consider using the singular form after the singular determiner “This”.
Context: ...koenig.de). ## Provides entities This integrations provides a set of {% term "Binary senso...

(AGREEMENT_SENT_START)

⏰ 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 (4)
source/_integrations/tankerkoenig.markdown (4)

19-21: Approve addition of the related section
The new related front matter neatly links to the common task on defining a custom polling interval, improving cross‑reference within the docs.


36-36: Approve inclusion of the config flow snippet
Embedding the integrations/config_flow.md template ensures consistent configuration instructions across integrations.


38-38: Approve use of configuration_basic directive
The configuration_basic block clearly organizes key setup parameters for users.


48-48: Approve stations description
The “Select the gas stations you want to add to Home Assistant” description is clear and concise.

@home-assistant home-assistant bot added the has-parent This PR has a parent PR in a other repo label Apr 21, 2025
Copy link
Contributor

@c0ffeeca7 c0ffeeca7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice addition to the docs! Thank you, @mib1185 👍

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
source/_integrations/tankerkoenig.markdown (1)

45-46: Duplicate fix for the Location description typo.
The phrase “was et during” still contains the typo flagged earlier; it should read “was set during.”

-    description: "Pick the location where to search for gas stations (_defaults to the location of your Home which was et during [onboarding](/getting-started/onboarding)_)"
+    description: "Pick the location where to search for gas stations (_defaults to the location of your home which was set during [onboarding](/getting-started/onboarding))_"
🧹 Nitpick comments (6)
source/_integrations/tankerkoenig.markdown (6)

25-25: Use the correct verb form “set up”.
In the intro sentence, change “and setup automations” → “and set up automations” to use “set up” as a verb.

-The `tankerkoenig` integration allows you to monitor the fuel prices with [tankerkoenig.de](https://www.tankerkoenig.de/) from within Home Assistant and setup automations based on the information.
+The `tankerkoenig` integration allows you to monitor the fuel prices with [tankerkoenig.de](https://www.tankerkoenig.de/) from within Home Assistant and set up automations based on the information.

29-31: Fix trailing space and ensure blank lines around lists.
Line 29 ends with an extra space, and list items are more readable with blank lines before/after. Consider:

-To use this integration, you need an API key from tankerkoenig. 
+To use this integration, you need an API key from tankerkoenig.

+1. Go to [tankerkoenig API](https://creativecommons.tankerkoenig.de) and in the top right, select **API‑KEY**.
+2. Fill out the form and request a free API key.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

29-29: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)


30-30: Lists should be surrounded by blank lines
null

(MD032, blanks-around-lists)


35-35: Improve phrasing of the conditional clause.
The phrase “If you consider to define a custom polling interval” is awkward. Use a gerund or rephrase:

-If you consider to [define a custom polling interval](/common-tasks/general/#defining-a-custom-polling-interval), then please keep in mind that requests should be limited to less than once every 5 minutes.
+When defining a custom polling interval, please keep in mind that requests should be limited to less than once every 5 minutes.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~35-~35: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...e issued otherwise. If you consider to [define a custom polling interval](/common-task...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


40-44: Standardize “API key” capitalization and style.
The description uses “API‑KEY”; for consistency, use “API key” (lowercase “key”) and remove underscores around the link:

-API Key:
-    description: "The tankerkoenig API-KEY to be used (_see [Prerequisites](#prerequisites)_)."
+API key:
+    description: "The tankerkoenig API key to be used (see [Prerequisites](#prerequisites))."

Also consider clarifying the default behavior (if any) for “Region name.”


53-61: Option flow block and descriptions.
The option_flow.md include is correct. However, in the “Show stations on map” description, “Weather” should be “Whether”:

-    description: "Weather to show the station sensors on the map or not."
+    description: "Whether to show the station sensors on the map or not."

66-69: Fix pluralization in “Provides entities”.
Change “This integrations provides” to the singular:

-This integrations provides a set of {% term "Binary sensor" %} and {% term Sensor %} entities for each selected gas station.
+This integration provides a set of {% term "Binary sensor" %} and {% term Sensor %} entities for each selected gas station.
🧰 Tools
🪛 LanguageTool

[grammar] ~67-~67: The singular determiner ‘this’ may not agree with the plural noun ‘integrations’. Did you mean “these”?
Context: ...ankerkoenig.de). ## Provides entities This integrations provides a set of {% term ...

(THIS_NNS)


[grammar] ~68-~68: Consider using the singular form after the singular determiner “This”.
Context: ...koenig.de). ## Provides entities This integrations provides a set of {% term "Binary senso...

(AGREEMENT_SENT_START)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e5774f5 and 0ffe111.

📒 Files selected for processing (1)
  • source/_integrations/tankerkoenig.markdown (1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/tankerkoenig.markdown

[uncategorized] ~35-~35: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...e issued otherwise. If you consider to [define a custom polling interval](/common-task...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


[grammar] ~67-~67: The singular determiner ‘this’ may not agree with the plural noun ‘integrations’. Did you mean “these”?
Context: ...ankerkoenig.de). ## Provides entities This integrations provides a set of {% term ...

(THIS_NNS)


[grammar] ~68-~68: Consider using the singular form after the singular determiner “This”.
Context: ...koenig.de). ## Provides entities This integrations provides a set of {% term "Binary senso...

(AGREEMENT_SENT_START)

🪛 markdownlint-cli2 (0.17.2)
source/_integrations/tankerkoenig.markdown

29-29: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)


30-30: Lists should be surrounded by blank lines
null

(MD032, blanks-around-lists)

⏰ 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 (4)
source/_integrations/tankerkoenig.markdown (4)

19-21: Verify “related” block placement and formatting.
The new related entry appears correctly indented within the frontmatter and follows the pattern used in other integrations.


27-27: Heading is correctly added.
The new “## Prerequisites” section aligns with the structure of other integration docs.


38-39: Include of config_flow.md is correct.
This matches the pattern for documenting the config flow across Home Assistant integrations.


47-50: Configuration parameters look good.
The “Search radius” and first “Stations” descriptions are clear and aligned with other integration docs.

@c0ffeeca7 c0ffeeca7 merged commit c5c8243 into home-assistant:current Apr 22, 2025
7 checks passed
@mib1185 mib1185 deleted the tankerkoening/improve-docs branch April 22, 2025 08:34
@github-actions github-actions bot locked and limited conversation to collaborators Apr 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
current This PR goes into the current branch has-parent This PR has a parent PR in a other repo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants