Skip to content

Adds new integration [b12e/ha_lynkco_2025]#6494

Open
b12e wants to merge 1 commit intohacs:masterfrom
b12e:add-lynkco
Open

Adds new integration [b12e/ha_lynkco_2025]#6494
b12e wants to merge 1 commit intohacs:masterfrom
b12e:add-lynkco

Conversation

@b12e
Copy link

@b12e b12e commented Mar 23, 2026

Checklist

  • I've read the publishing documentation.
  • I've added the HACS action to my repository.
  • I've added the hassfest action to my repository.
  • The actions are passing without any disabled checks in my repository.
  • I've added a link to the action run on my repository below in the links section.
  • I've created a new release of the repository after the validation actions were run successfully.

Links

Link to current release: https://github.com/b12e/ha_lynkco_2025/releases/tag/v0.2.5
Link to successful HACS action (without the ignore key): https://github.com/b12e/ha_lynkco_2025/actions/runs/23451914367/job/68231016208
Link to successful hassfest action (if integration): https://github.com/b12e/ha_lynkco_2025/actions/runs/23451914367/job/68231016211

@hacs-bot hacs-bot bot marked this pull request as draft March 23, 2026 17:56
Copy link

@hacs-bot hacs-bot bot left a comment

Choose a reason for hiding this comment

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

Remove "HACS" from your repository name. Repository names cannot contain "HACS" to avoid confusion with the official HACS project. Please rename your repository and update this PR.

@b12e b12e marked this pull request as ready for review March 23, 2026 18:01
@hacs-bot hacs-bot bot changed the title Add Lynk & Co integration (b12e/hacs_lynkco_2025) Adds new integration [b12e/ha_lynkco_2025] Mar 23, 2026
@hacs-bot
Copy link

hacs-bot bot commented Mar 23, 2026

Thank you for submitting your repository to HACS (Home Assistant Community Store).

Your submission is in the review queue:
Your repository is waiting to be reviewed and included in HACS.

You can view the current queue here. Pull requests are processed in the order they were created, oldest first.

What to avoid during review:
To help reviewers work efficiently, don't do the following:

  • Comment on the pull request - The reviewer will contact you when they have feedback or questions.
  • Open a new pull request - This won't speed up the process and creates duplicate work.
  • Ask followers to comment on the pull request - This won't speed up the process and may delay your review.
  • Merge in the default branch - Only do this if a maintainer asks you to resolve a merge conflict.

If you need to make changes:
You can continue updating your repository while waiting for review. Changes to your repository will be reflected when the reviewer examines it. Only comment on the pull request if you need to withdraw your submission or have critical information for reviewers.

About draft pull requests:
Draft pull requests aren't included in the review queue. Your pull request may be marked as draft by a reviewer if issues need to be addressed. Once you've resolved all issues, mark it as ready for review to re-enter the queue.

What happens next:
Once a reviewer examines your submission, they'll either:

  • Approve and merge your pull request if everything meets the requirements
  • Request changes or ask questions if adjustments are needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant