Skip to content

ci: fix pre-commit EOF + TOC push permission #2

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.

Sign up for GitHub

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

Merged
CaseyRo merged 1 commit into from
Jul 9, 2026
Merged

ci: fix pre-commit EOF + TOC push permission #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/toc.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ jobs:
generateTOC:
name: TOC Generator
runs-on: ubuntu-latest
permissions:
contents: write
steps:
- uses: technote-space/toc-generator@v4
with:
Expand Down
1 change: 0 additions & 1 deletion openspec/specs/options-flow/spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -264,4 +264,3 @@ On `async_setup_entry`, the integration SHALL scan the entity registry for entit
- **WHEN** the integration runs the sleep-switch cleanup
- **AND** another integration owns a similarly named entity (e.g., a user-created `switch.adaptive_lighting_sleep_mode_demo` template switch)
- **THEN** that foreign entity SHALL NOT be removed from the entity registry

1 change: 0 additions & 1 deletion openspec/specs/runtime-range-controls/spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,4 +195,3 @@ Moving the slider SHALL NOT trigger an integration reload, matching the no-reloa
- **WHEN** the curve is evaluated 45 minutes after today's sunset
- **THEN** the day-anchoring SHALL still resolve the pair to today's events
- **AND** the computed brightness SHALL lie strictly between the profile's minimum and maximum (the down-ramp is still in progress, not snapped to minimum)

Loading