Conversation
Signed-off-by: Pieter Viljoen <ptr727@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR improves the README.md documentation by enhancing clarity and consistency across setup instructions and branching workflow sections.
Changes:
- Separated Visual Studio Code and Visual Studio installation instructions into distinct bullet points for better clarity
- Updated links and descriptions for GitHub Local Actions setup to be more specific and clear
- Enhanced branching workflow instructions with better clarity on branch protection and merge strategies
Signed-off-by: Pieter Viljoen <ptr727@users.noreply.github.com>
ptr727
added a commit
that referenced
this pull request
Jul 17, 2026
Reconcile the stale `HomeAssistant-Config` registry `driftNotes` after the [`#16`](ptr727/HomeAssistant-Config#16) operational onboarding. Mirrors the `#329` reconciliation for Vantage-Config. ## What changed The prior driftNotes described work that is now complete and planned a `groundTruthBranch` flip that is declined: - "develop is behind main by 2 commits / fast-forward then flip groundTruthBranch to develop" - develop is content-ahead; the flip is **declined** (see below). - "pending: lint CI" - `test-pull-request.yml` with the `Check pull request workflow status job` required check is live. - "pending: dispatch-only source-release scaffolding (version.json + publish-release.yml)" - both present. Replaced with a completed-onboarding summary: baseline carried (repo-config operational, `AUDIT.md`, `spec/secrets.json`, App-signed Dependabot merge-bot) and promoted `develop -> main` via HomeAssistant-Config PR `#17`. Self-audit verified in sync (settings, both rulesets, `CODEGEN_APP_*` present in both stores). ## groundTruthBranch stays `main` (deliberate) Kept `groundTruthBranch: main`, **not** flipped to `develop`. develop is the working branch (direct signed commits); main is the promoted stable snapshot the audit should target. This is a deliberate divergence from the other operational repos (Vantage-Config / ESPHome-Config / HomeAutomation-Config use `develop`); the broader convention question is raised in #340. ## Findings note (context, see #341) The `#16` audit block was stale: the `CODEGEN_APP_*` secrets were already present in both stores and develop was already ahead of main. Only the `repo-config/... absent` LETTER finding was real, and it is now cleared on `main` by PR `#17`. Validation: `jq` parses clean, `spec/validate.py` -> "21 cataloged, 0 backlog repos classify cleanly." 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Signed-off-by: Pieter Viljoen ptr727@users.noreply.github.com