Adds the missing deploy-woodpecker-agent pipeline so the agent role (incl. the Docker IPv6 daemon.json from #48) actually reaches the agents via CI — mirrors the other deploy-* pipelines.
Merging self-triggers it; it restarts Docker on the agents (brief CI blip, may self-report failure) but applies the v6 config on both. Then deploy-netbird-proxy can reach the v6-only proxy-1.
🤖 Generated with Claude Code
Adds the missing `deploy-woodpecker-agent` pipeline so the agent role (incl. the Docker IPv6 `daemon.json` from #48) actually reaches the agents via CI — mirrors the other `deploy-*` pipelines.
Merging self-triggers it; it restarts Docker on the agents (brief CI blip, may self-report failure) but applies the v6 config on both. Then `deploy-netbird-proxy` can reach the v6-only proxy-1.
🤖 Generated with Claude Code
The woodpecker-agent role had no deploy pipeline — so the Docker IPv6
daemon.json (PR #48) landed in git but never reached the agents. Mirror
the other deploy-* pipelines: master + manual trigger, runs
install-woodpecker-agent.yml in the ci-ansible runner.
Merging self-triggers on its own path and applies the agent config. It
deploys the agents from an agent, so the Docker restart kills this job
mid-run (reported as failure) but still applies on both agents; re-trigger
deploy-netbird-proxy after.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds the missing
deploy-woodpecker-agentpipeline so the agent role (incl. the Docker IPv6daemon.jsonfrom #48) actually reaches the agents via CI — mirrors the otherdeploy-*pipelines.Merging self-triggers it; it restarts Docker on the agents (brief CI blip, may self-report failure) but applies the v6 config on both. Then
deploy-netbird-proxycan reach the v6-only proxy-1.🤖 Generated with Claude Code