Repository navigation
Conversation
8 of 15 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed change
Integrations can keep their issue guidance in core as
homeassistant/components/<domain>/issue_context.md. The bot reads it from dev, the file wins over the map entry. A text change is then a normal core PR, no bot release.Reading from dev now shares one cache with
manifest.json. Only a 404 counts as a miss there now, other errors keep the last value.The map stays until core has the files. Draft until the core team has had a look, see #130.
Type of change
Additional information
Checklist
mise run test). Your PR cannot be merged unless tests pass.mise run check).mise run format).If behaviour, configuration, or environment variables changed:
README.mdand.env.examplehave been updated accordingly.