Skip to content
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

Update Assist section for 2024.12 release #36045

Open
wants to merge 7 commits into
base: rc
Choose a base branch
from

Conversation

jlpouffier
Copy link
Contributor

@jlpouffier jlpouffier commented Nov 28, 2024

Proposed change

Update the Assist section on the 2024.12 release notes.

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

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

  • New Features

    • Introduced a section highlighting contributions from language leaders to enhance voice assistant capabilities.
    • Updated the "Voice" section to clarify local processing integration with LLM-based agents.
  • Improvements

    • Enhanced explanations in the "A faster voice experience" section regarding the HASSIL intent parser's speed.
    • Revised the "Integration Quality Scale" for better user experience focus.
  • Documentation

    • Improved clarity and readability of release notes with minor formatting adjustments.

@home-assistant home-assistant bot added in-progress This PR/Issue is currently being worked on needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch rc This PR is against the RC branch labels Nov 28, 2024
@home-assistant
Copy link

It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the current branch. Please change the target branch of this PR to current and rebase if needed. If this is documentation for a new feature, please add a link to that PR in your description.

Copy link

netlify bot commented Nov 28, 2024

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit a7de4b5
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/6749c47daa88230008088cb0
😎 Deploy Preview https://deploy-preview-36045--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 Nov 28, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request involve updates to the beta release notes for Home Assistant version 2024.12. Key additions include a new section on contributions from language leaders to voice assistant capabilities, rephrased content in the "Voice" section for clarity, and refinements in the "A faster voice experience" section regarding the HASSIL intent parser. The "Revised Integration Quality Scale" section has been clarified, and minor formatting adjustments have been made throughout the document to enhance readability.

Changes

File Path Change Summary
source/_posts/2024-12-04-release-202412.markdown - Added a section on contributions from language leaders.
- Rephrased sentences in the "Voice" section for clarity regarding local processing and LLMs.
- Refined the "A faster voice experience" section to explain improvements to the HASSIL intent parser.
- Updated the "Revised Integration Quality Scale" section for clarity on new tiers.
- Made minor formatting changes, including bullet points and removal of redundant phrases.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant VoiceAssistant
    participant LLM
    participant HASSILParser

    User->>VoiceAssistant: Issue voice command
    VoiceAssistant->>HASSILParser: Process command locally
    HASSILParser-->>VoiceAssistant: Return processed command
    VoiceAssistant->>LLM: Forward complex queries
    LLM-->>VoiceAssistant: Return response
    VoiceAssistant-->>User: Provide feedback
Loading

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

🧹 Outside diff range and nitpick comments (3)
source/_posts/2024-12-04-release-202412.markdown (3)

131-144: Grammar and clarity improvements needed

Several grammatical issues need to be addressed:

  • Line 138: "set-up" should be "set up" when used as a verb
  • Line 141: "This allow" should be "This allows"
  • Line 142: "non" should be "none"
-This choice was an interesting first step. LLMs are generally much smarter and knowledgeable about the world than our built-in intents. However, they are often slow and/or expensive. And let's face it, even if the demos are cool, 90% of the commands we say in our homes are simple _"Turn this on"_, _"Turn that off"_.
+This was an important first step. While LLMs are more versatile and knowledgeable than our built-in intents, they can be slow and expensive. In practice, most voice commands in our homes are simple, like _"Turn this on"_ or _"Turn that off"_.

-Starting from this release, you can set-up a voice assistant in a way that will target our fast, community driven, built-in intents first, and only fallback to a LLM-based agent if no matches were found.
+Starting from this release, you can set up a voice assistant to use our fast, community-driven, built-in intents first, and only fall back to a LLM-based agent if no matches are found.

-This allow you to mix the pros of both worlds with almost non of the cons.
+This allows you to combine the best of both worlds with almost none of the drawbacks.
🧰 Tools
🪛 LanguageTool

[grammar] ~138-~138: The word “set-up” is a noun. The verb is spelled with a space.
Context: ...ds. Starting from this release, you can set-up a voice assistant in a way that will ta...

(NOUN_VERB_CONFUSION)


[grammar] ~141-~141: Possible subject-verb agreement error detected.
Context: .../images/blog/2024-12/llm-fallback.png) This allow you to mix the pros of both worlds with...

(THIS_THAT_AGR)


[misspelling] ~142-~142: Did you mean “none”?
Context: ...mix the pros of both worlds with almost non of the cons. Specific known commands w...

(NON_NONE)


[style] ~144-~144: Consider replacing ‘only’ with a different word to let your writing stand out.
Context: ...emely fast, and the power of a LLM will only be used for more complex queries that H...

(ONLY_EXCLUSIVELY_STYLE)


150-161: Improve wording and grammar in language leaders section

The section needs refinement in its wording:

  • Line 154: "amount of contributions" should be "number of contributions"
  • Line 154: "contributions on our" should be "contributions to our"
-The amount of contributions on our [intents repository] (where we store the supported sentences) skyrocketed during the last month.
+The number of contributions to our [intents repository] (where we store the supported sentences) has skyrocketed over the last month.

-More and more language are becoming usable, or even complete!
+More and more languages are becoming usable, or even complete!
🧰 Tools
🪛 LanguageTool

[uncategorized] ~154-~154: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...mely hard to polish their language. The amount of contributions on our [intents reposi...

(AMOUNTOF_TO_NUMBEROF)


[grammar] ~154-~154: The usual preposition for “contribution” is “to”. Did you mean “contributions to”?
Context: ...to polish their language. The amount of contributions on our [intents repository] (where we stor...

(ON_THE_NOVEL)


Line range hint 1-24: Address remaining TODO comments

Several TODO items need to be addressed before the final release:

  1. Introduction paragraph in the Voice section
  2. Demonstration videos in multiple sections
  3. Processing of potential changes (noted in the "Potential changes to process" section)

Would you like me to help create GitHub issues to track these remaining tasks?

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between adac966 and dc5ebaf.

⛔ Files ignored due to path filters (1)
  • source/images/blog/2024-12/llm-fallback.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • source/_posts/2024-12-04-release-202412.markdown (2 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_posts/2024-12-04-release-202412.markdown

[grammar] ~138-~138: The word “set-up” is a noun. The verb is spelled with a space.
Context: ...ds. Starting from this release, you can set-up a voice assistant in a way that will ta...

(NOUN_VERB_CONFUSION)


[grammar] ~141-~141: Possible subject-verb agreement error detected.
Context: .../images/blog/2024-12/llm-fallback.png) This allow you to mix the pros of both worlds with...

(THIS_THAT_AGR)


[misspelling] ~142-~142: Did you mean “none”?
Context: ...mix the pros of both worlds with almost non of the cons. Specific known commands w...

(NON_NONE)


[style] ~144-~144: Consider replacing ‘only’ with a different word to let your writing stand out.
Context: ...emely fast, and the power of a LLM will only be used for more complex queries that H...

(ONLY_EXCLUSIVELY_STYLE)


[uncategorized] ~154-~154: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...mely hard to polish their language. The amount of contributions on our [intents reposi...

(AMOUNTOF_TO_NUMBEROF)


[grammar] ~154-~154: The usual preposition for “contribution” is “to”. Did you mean “contributions to”?
Context: ...to polish their language. The amount of contributions on our [intents repository] (where we stor...

(ON_THE_NOVEL)


[style] ~170-~170: ‘On top of that’ might be wordy. Consider a shorter alternative.
Context: ...ered the way we are matching sentences. On top of that, language leaders spent some time reduc...

(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)

🔇 Additional comments (1)
source/_posts/2024-12-04-release-202412.markdown (1)

165-173: Add specific performance metrics and demonstration video

The section would benefit from:

  1. Specific performance metrics showing the improvement (e.g., "Processing time reduced from X to Y seconds")
  2. The demonstration video needs to be added (TODO on line 175)

Would you like me to help create a GitHub issue to track the addition of the demonstration video?

🧰 Tools
🪛 LanguageTool

[style] ~170-~170: ‘On top of that’ might be wordy. Consider a shorter alternative.
Context: ...ered the way we are matching sentences. On top of that, language leaders spent some time reduc...

(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)

synesthesiam
synesthesiam previously approved these changes Nov 28, 2024
source/_posts/2024-12-04-release-202412.markdown Outdated Show resolved Hide resolved
source/_posts/2024-12-04-release-202412.markdown Outdated Show resolved Hide resolved
source/_posts/2024-12-04-release-202412.markdown Outdated Show resolved Hide resolved
source/_posts/2024-12-04-release-202412.markdown Outdated Show resolved Hide resolved
source/_posts/2024-12-04-release-202412.markdown Outdated Show resolved Hide resolved
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

🧹 Outside diff range and nitpick comments (4)
source/_posts/2024-12-04-release-202412.markdown (4)

138-138: Fix grammar: "set-up" should be "set up" when used as a verb

The word "set-up" is a noun, while "set up" is the correct verb form.

-Starting from this release, you can set-up a voice assistant
+Starting from this release, you can set up a voice assistant
🧰 Tools
🪛 LanguageTool

[grammar] ~138-~138: The word “set-up” is a noun. The verb is spelled with a space.
Context: ...ds. Starting from this release, you can set-up a voice assistant in a way that will ta...

(NOUN_VERB_CONFUSION)


142-142: Fix subject-verb agreement

The singular subject "This" requires the verb "allows".

-This allow you to mix the pros of both worlds
+This allows you to mix the pros of both worlds

154-154: Improve word choice and preposition usage

Two improvements needed:

  1. Use "number of" instead of "amount of" when referring to countable items
  2. Use "contributions to" instead of "contributions on"
-The amount of contributions on our [intents repository]
+The number of contributions to our [intents repository]
🧰 Tools
🪛 LanguageTool

[uncategorized] ~154-~154: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...mely hard to polish their language. The amount of contributions on our [intents reposi...

(AMOUNTOF_TO_NUMBEROF)


[grammar] ~154-~154: The usual preposition for “contribution” is “to”. Did you mean “contributions to”?
Context: ...to polish their language. The amount of contributions on our [intents repository] (where we stor...

(ON_THE_NOVEL)


144-144: Address remaining TODO placeholders

The following TODO items need to be completed before the final release:

  1. Video demonstration for LLM fallback feature
  2. Video demonstration for faster voice experience

Would you like me to help create a structured outline for these demonstration videos?

Also applies to: 177-177

🧰 Tools
🪛 LanguageTool

[style] ~144-~144: Consider replacing ‘only’ with a different word to let your writing stand out.
Context: ...emely fast, and the power of a LLM will only be used for more complex queries that H...

(ONLY_EXCLUSIVELY_STYLE)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between dc5ebaf and 70b8476.

📒 Files selected for processing (1)
  • source/_posts/2024-12-04-release-202412.markdown (2 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_posts/2024-12-04-release-202412.markdown

[grammar] ~138-~138: The word “set-up” is a noun. The verb is spelled with a space.
Context: ...ds. Starting from this release, you can set-up a voice assistant in a way that will ta...

(NOUN_VERB_CONFUSION)


[grammar] ~141-~141: Possible subject-verb agreement error detected.
Context: .../images/blog/2024-12/llm-fallback.png) This allow you to mix the pros of both worlds with...

(THIS_THAT_AGR)


[style] ~144-~144: Consider replacing ‘only’ with a different word to let your writing stand out.
Context: ...emely fast, and the power of a LLM will only be used for more complex queries that H...

(ONLY_EXCLUSIVELY_STYLE)


[uncategorized] ~154-~154: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...mely hard to polish their language. The amount of contributions on our [intents reposi...

(AMOUNTOF_TO_NUMBEROF)


[grammar] ~154-~154: The usual preposition for “contribution” is “to”. Did you mean “contributions to”?
Context: ...to polish their language. The amount of contributions on our [intents repository] (where we stor...

(ON_THE_NOVEL)


[uncategorized] ~170-~170: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ..., we completely reengineered the way we are matching sentences. On top of that, language lea...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)


[style] ~170-~170: ‘On top of that’ might be wordy. Consider a shorter alternative.
Context: ...ered the way we are matching sentences. On top of that, language leaders spent some time reduc...

(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)

🔇 Additional comments (2)
source/_posts/2024-12-04-release-202412.markdown (2)

170-171: Improve technical clarity and grammar

Two improvements needed:

  1. Fix verb tense
  2. Consider adding specific performance metrics
-we completely reengineered the way we are matching sentences.
+we completely reengineered the way we match sentences.

Could you provide specific performance metrics for the sentence matching improvements? This would help users understand the magnitude of the optimization.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~170-~170: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ..., we completely reengineered the way we are matching sentences. On top of that, language lea...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)


[style] ~170-~170: ‘On top of that’ might be wordy. Consider a shorter alternative.
Context: ...ered the way we are matching sentences. On top of that, language leaders spent some time reduc...

(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)


152-152: Consider rephrasing the hardware announcement

The current phrasing about hardware coming "very soon" might set specific expectations. Consider a more general statement unless there's a confirmed release date.

✅ Verification successful

Based on the extensive search results, I can see that this line is part of a blog post announcing upcoming hardware, specifically voice assistant hardware. The context shows that Home Assistant has been working on voice capabilities throughout 2023 (Year of the Voice) and into 2024, with multiple "chapters" of voice-related features and improvements. The hardware announcement appears to be intentional and part of a planned rollout.

The hardware announcement is appropriate to keep

The current phrasing about hardware coming "very soon" is actually accurate and intentional, as evidenced by:

  1. Multiple references in the search results about upcoming voice hardware
  2. A teaser image shown in the 2024 H2 roadmap post
  3. Consistent messaging about voice hardware development throughout the codebase
  4. The announcement being part of an official release notes post
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if there are any official announcements or confirmed dates
gh issue list -R home-assistant/core -l "hardware" --json title,body -q '.[].title'

Length of output: 83


Script:

#!/bin/bash
# Let's check the blog post content for any other mentions of hardware announcements
rg -i "hardware" "source/_posts/2024-12-04-release-202412.markdown"

# Also check recent blog posts for hardware-related announcements
fd "202[34].*\.markdown$" source/_posts/ -x rg -i "hardware|voice" {}

Length of output: 108892

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

🧹 Outside diff range and nitpick comments (3)
source/_posts/2024-12-04-release-202412.markdown (3)

128-129: Fix grammar issues in the Voice section

Several grammar issues need to be addressed:

  • Lines 128-129: Replace "let" with "allow" for better clarity
  • Line 138: "set-up" should be "set up" when used as a verb
  • Line 142: "allow" should be "allows" to agree with the singular subject "This"
-wonderful (and scary) world of LLMs. We allowed you to let an LLM agent control
+wonderful (and scary) world of LLMs. We allowed you to allow an LLM agent to control

-Starting from this release, you can set-up a voice assistant
+Starting from this release, you can set up a voice assistant

-This allow you to mix the pros of both worlds
+This allows you to mix the pros of both worlds

Also applies to: 138-138, 142-142


154-154: Improve technical writing in the Language leaders section

The sentence structure needs improvement:

  • Use "number of" instead of "amount of" when referring to countable contributions
  • Use "to" instead of "on" when referring to contributions to a repository
-The amount of contributions on our [intents repository]
+The number of contributions to our [intents repository]
🧰 Tools
🪛 LanguageTool

[uncategorized] ~154-~154: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...mely hard to polish their language. The amount of contributions on our [intents reposi...

(AMOUNTOF_TO_NUMBEROF)


[grammar] ~154-~154: The usual preposition for “contribution” is “to”. Did you mean “contributions to”?
Context: ...to polish their language. The amount of contributions on our [intents repository] (where we stor...

(ON_THE_NOVEL)


170-171: Improve technical clarity in the HASSIL section

The description could be more concise and technically precise:

-This release adds a lot of love to HASSIL, we completely reengineered the way we are matching sentences.
-On top of that, language leaders spent some time reducing the complexity of their sentences,
+This release significantly improves HASSIL's performance through a complete reengineering of sentence matching.
+Additionally, language leaders optimized sentence patterns,
🧰 Tools
🪛 LanguageTool

[style] ~170-~170: ‘On top of that’ might be wordy. Consider a shorter alternative.
Context: ...ered the way we are matching sentences. On top of that, language leaders spent some time reduc...

(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 70b8476 and a7de4b5.

📒 Files selected for processing (1)
  • source/_posts/2024-12-04-release-202412.markdown (2 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_posts/2024-12-04-release-202412.markdown

[grammar] ~138-~138: The word “set-up” is a noun. The verb is spelled with a space.
Context: ...ds. Starting from this release, you can set-up a voice assistant in a way that will ta...

(NOUN_VERB_CONFUSION)


[grammar] ~141-~141: Possible subject-verb agreement error detected.
Context: .../images/blog/2024-12/llm-fallback.png) This allow you to mix the pros of both worlds with...

(THIS_THAT_AGR)


[style] ~144-~144: Consider replacing ‘only’ with a different word to let your writing stand out.
Context: ...mely fast, and the power of an LLM will only be used for more complex queries that H...

(ONLY_EXCLUSIVELY_STYLE)


[uncategorized] ~154-~154: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...mely hard to polish their language. The amount of contributions on our [intents reposi...

(AMOUNTOF_TO_NUMBEROF)


[grammar] ~154-~154: The usual preposition for “contribution” is “to”. Did you mean “contributions to”?
Context: ...to polish their language. The amount of contributions on our [intents repository] (where we stor...

(ON_THE_NOVEL)


[style] ~170-~170: ‘On top of that’ might be wordy. Consider a shorter alternative.
Context: ...ered the way we are matching sentences. On top of that, language leaders spent some time reduc...

(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in-progress This PR/Issue is currently being worked on needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch rc This PR is against the RC branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants