Skip to content

Adds new plugin [infernalK/ha-schedule-manager-card]#8711

Open
infernalK wants to merge 3 commits into
hacs:masterfrom
infernalK:add-schedule-manager-card
Open

Adds new plugin [infernalK/ha-schedule-manager-card]#8711
infernalK wants to merge 3 commits into
hacs:masterfrom
infernalK:add-schedule-manager-card

Conversation

@infernalK

@infernalK infernalK commented Jun 23, 2026

Copy link
Copy Markdown

Checklist

  • I've read the publishing documentation.
  • I've added the HACS 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/infernalK/ha-schedule-manager-card/releases/tag/v0.1.0

Link to successful HACS action (without the ignore key): https://github.com/infernalK/ha-schedule-manager-card/actions/runs/28011270745/job/82904766482

Related integration (installed separately): https://github.com/infernalK/ha-schedule-manager

@hacs-bot hacs-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Your branch seems out of date. Please update your branch with the latest changes from the base branch.

@hacs-bot hacs-bot Bot marked this pull request as draft June 23, 2026 08:01
Co-authored-by: Cursor <cursoragent@cursor.com>
@infernalK infernalK force-pushed the add-schedule-manager-card branch from 53bb09e to 7f021be Compare June 23, 2026 08:59
Co-authored-by: Cursor <cursoragent@cursor.com>
@infernalK infernalK marked this pull request as ready for review June 23, 2026 09:25
@hacs-bot

hacs-bot Bot commented Jun 23, 2026

Copy link
Copy Markdown

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

Co-authored-by: Cursor <cursoragent@cursor.com>
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