Skip to content

fix(ci): rebuild claude-code when its managed skill or agent-browser config changes - #205

Open
gatezh wants to merge 1 commit into
masterfrom
fix/claude-code-build-paths
Open

gatezh wants to merge 1 commit into
masterfrom
fix/claude-code-build-paths

Conversation

@gatezh

@gatezh gatezh commented Oct 8, 2026

Copy link
Copy Markdown
Owner

What

Rebuild and publish claude-code when its managed browser skill or agent-browser config changes on master.

Why

#175 added two files the image copies in, managed-skills/devcontainer-browser/SKILL.md and agent-browser.json. build-claude-code.yml only triggers on Dockerfile, *.sh and managed-settings.json, so an edit to either file alone would merge and never be published. #175 itself was published only because it also changed the Dockerfile.

Changes

  • Add claude-code/.devcontainer/managed-skills/** and claude-code/.devcontainer/agent-browser.json to the push.paths of build-claude-code.yml. That list now matches every local file the Dockerfile COPYs in.

Notes

  • PR CI is unaffected: its change detection already uses claude-code/**.
  • The paths stay explicit rather than claude-code/.devcontainer/**, so template-only files (devcontainer.json, docker-compose.yml, claude-sandbox/) don't trigger image rebuilds. ralphex-fe's list follows the same pattern.

…config changes

#175 added two files the image copies in, managed-skills/devcontainer-browser/SKILL.md
and agent-browser.json, but build-claude-code.yml's push paths didn't include them.
An edit to either alone would merge to master and never be published.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant