One gate for local pushes and CI (scripts/check.sh: doc limits, secret scan, build, tests), Drone and Dockerfile removed, deploy-gateway.sh with health check and rollback (tested against stubs, not yet run on the Pi), /ship and /close-milestone skills. The backend image moves to M3. 🤖 Generated with Claude Code
One gate for local pushes and CI (scripts/check.sh: doc limits, secret scan, build, tests), Drone and Dockerfile removed, deploy-gateway.sh with health check and rollback (tested against stubs, not yet run on the Pi), /ship and /close-milestone skills. The backend image moves to M3. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Runs doc line limits from CONTRIBUTING.md, a secret scan over tracked
files and the Maven build with tests. The pre-push hook and CI will both
call it, so a push that passes locally passes in CI.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Both gates now run the same script instead of CI running only the tests.
The hook lives in .githooks so it is versioned; each clone enables it once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Gitea Actions replaced Drone, and the Dockerfile packaged a Java 11 image
of a jar that runs on the Pi, not in Docker. The backend image comes with
the backend itself.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deploys only a clean master that matches origin, checks ssh and sudo on
the Pi before touching anything, swaps the jar, restarts the service and
keeps the previous jar. /health reports UP for minutes after a start even
without a read, so the script also requires the process to survive 30 s
without systemd restarting it; otherwise it restores the previous jar.
The version is tagged only after a healthy start.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Both workflows repeat for every PR and milestone; written down once they
follow CONTRIBUTING.md the same way each time, including when a deploy
needs the user's approval.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The backend does not exist yet, so CI has no image to build; it comes
with the backend in M3. The deploy item stays open until the script has
run once on the Pi.
Co-Authored-By: Claude Opus 5.5 <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.
One gate for local pushes and CI (scripts/check.sh: doc limits, secret scan, build, tests), Drone and Dockerfile removed, deploy-gateway.sh with health check and rollback (tested against stubs, not yet run on the Pi), /ship and /close-milestone skills. The backend image moves to M3. 🤖 Generated with Claude Code
Pull request closed