Jan Novak
076bc66ebe
Bootstraps the empty repo into a kubebuilder go/v4 project: group crawl.example.com, version v1alpha1, kind Proxy (namespaced). Keeps the existing module path and preserves the repo's Go/testing/changelog conventions from CLAUDE.md untouched. Drops the scaffolded GitHub Actions workflows since the remote is Gitea, not GitHub. Everything else is default kubebuilder output, unmodified, so later diffs stay reviewable against a known baseline. Full implementation plan: docs/plans/2026-08-07-1747-proxy-operator.md Co-Authored-By: Claude <noreply@anthropic.com>
11 lines
659 B
Markdown
11 lines
659 B
Markdown
Commit all staged and unstaged changes into git, assign the next tag in sequence, then ask for confirmation before pushing.
|
|
|
|
Before committing, check the current branch (`git branch --show-current`). If it's
|
|
`main`, follow CLAUDE.md's Branching & Merge Requests exceptions (small fixes,
|
|
typos/formatting, or explicit user request) — otherwise stop and ask, since releases
|
|
are not one of the documented straight-to-main cases.
|
|
|
|
No tagging scheme (semver vs. calver, `v` prefix, etc.) is documented in CLAUDE.md
|
|
yet — infer the existing pattern from `git tag --list` if any tags exist, otherwise
|
|
ask the user which scheme to start with instead of guessing.
|