cluster-autoscaler-with-capi/.claude/commands/ship.md at main

Files

T

kacerrandClaude Opus 5.5 5fd998c5f9 Initial import: phase docs, configs, Claude conventions

Phase 1-3 runbooks and design notes, version pins, config templates,
project-history conventions, cluster-inspector read-only credentials setup.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-27 00:58:52 +02:00

1.3 KiB

Raw Permalink Blame History

description

description
Commit current changes and push to the remote

Commit the current working-tree changes and push them.

Run git status and git diff to see what will be committed.
Check the staged content for secrets: Proxmox token secrets, kubeconfig contents, anything .gitignore would have caught by name but that was pasted into a doc. Stop and report if found.
Check the current branch (git branch --show-current). Docs, configs and history files may go straight to main. If on main and the diff contains phase-3 Go code or something the user called a feature, stop and tell the user to branch first (CLAUDE.md "Git").
If an approved plan is in progress, make sure its execution log in docs/plans-executions/ is updated and its checklist ticked for the steps included in this commit.
Stage the changed files (git add -A is fine here).
Commit with a short message inferred from the diff, ending with the Co-Authored-By: trailer for Claude. Pass the message via a HEREDOC.
Push with git push; if the branch has no upstream, git push -u origin HEAD.
If the branch isn't main, remind the user to open an MR with tea pr create rather than opening one automatically.
Report the commit hash and push result.

If there are no changes, stop and say so; do not create an empty commit.

1.3 KiB Raw Permalink Blame History

1.3 KiB

Raw Permalink Blame History