add garagedoor to build.yml and ci.yml

Walkthrough

The changes involve updates to two YAML configuration files within the GitHub workflows. The .github/workflows/build.yml file now includes a reference to esphome/garagedoor.yaml, expanding the list of configuration files processed during the build. Additionally, the .github/workflows/ci.yml file has been updated to include the repository esphome/garagedoor in the continuous integration jobs, thereby broadening the scope of the CI workflow.

Changes

File	Change Summary
.github/workflows/build.yml	Added `esphome/garagedoor.yaml` to the list of configuration files.
.github/workflows/ci.yml	Added `esphome/garagedoor` to the list of repositories in jobs.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CI Workflow
    participant Build Process

    User->>CI Workflow: Trigger CI
    CI Workflow->>Build Process: Start build
    Build Process->>Build Process: Process luxmeter.yaml
    Build Process->>Build Process: Process vindriktning.yaml
    Build Process->>Build Process: Process bluetoothproxy.yaml
    Build Process->>Build Process: Process garagedoor.yaml
    Build Process-->>CI Workflow: Build complete
    CI Workflow-->>User: Notify build status

🐰 In the garden, changes sprout,
New files and paths, there's no doubt!
Garagedoor joins the merry crew,
With workflows bright, and skies so blue.
Hops of joy, let’s celebrate,
Integration’s here, it’s truly great! 🌼

Recent review details

**Configuration used: CodeRabbit UI** **Review profile: CHILL**

Commits

Files that changed from the base of the PR and between 24292201db0c55167d200cfd41c26a62bcf8caee and 82a7ff5950c8c433af5b78660f5daed392fae529.

Files selected for processing (2)

* .github/workflows/build.yml (1 hunks) * .github/workflows/ci.yml (1 hunks)

Additional comments not posted (2)

.github/workflows/ci.yml (1)
`22-22`: **LGTM!** The change is consistent with the PR objective and is implemented correctly. It will expand the CI workflow to include the `esphome/garagedoor` repository.

.github/workflows/build.yml (1)
`21-21`: **LGTM!** The change is adding a new file `esphome/garagedoor.yaml` to the list of files to be built by the workflow. This is consistent with the existing pattern and is unlikely to have any negative impact on the workflow functionality.

--- 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?

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: -- `I pushed a fix in commit , 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 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` 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

scns / myESPhome