Repository navigation
Operational repos should pull the current develop branch before working on any new tasks #1415
Description
Operational repose. e.g. ESPHome-Config or HomeAssistant-Config, always operate with the develop branch as the active configuration, and should always pull the current develop branch before working on any new tasks, so that dependabot or other git only changes can be pulled to the local repo and avoid local work looking at stale code.
Activity
ptr727 commentedon Nov 1, 2026
Released (2026-11-02): worktree and branch removed, so this claim holds no files. Not fixed: this issue has no recorded maintainer answer, so the fix would add a rule nobody requested. It returns to the ranking held back as a question for the maintainer.
Backlog burndown claim (round 2, group R2G2). Branch:
feature/burn-3772. Issues: #3772, #3771, #3773, #1276, #1307, #1415, #3780.Predicted file set:
GOVERNANCE.md.agents/skills/backlog-burndown/and its generated trees (.github/skills/backlog-burndown/,.claude-plugin/fleet-skills/skills/backlog-burndown/,.claude-plugin/fleet-skills/.source-digests/backlog-burndown).agents/skills/branching-and-release-model/and its generated trees (.github/skills/branching-and-release-model/,.claude-plugin/fleet-skills/skills/branching-and-release-model/,.claude-plugin/fleet-skills/.source-digests/branching-and-release-model).agents/skills/git-commit-conventions/and its generated trees (.github/skills/git-commit-conventions/,.claude-plugin/fleet-skills/skills/git-commit-conventions/,.claude-plugin/fleet-skills/.source-digests/git-commit-conventions)Mark Direct-Push Closures and Close backlog-burndown Cleanup and Clai…
ptr727 commentedon Nov 2, 2026
Maintainer answer (backlog-burndown run, 2026-11-02): closed, because existing rules already cover it.
repo-worktreerequires every task, operational repositories included, to fetch immediately before creating its worktree and to base it onorigin/develop. So agent work never starts from a stale tree, and Dependabot or other git-only changes are always picked up. Post-merge cleanup also fast-forwards the base clone todevelop. The primary checkout itself stays the maintainer's.