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>
23 lines
1.1 KiB
Markdown
23 lines
1.1 KiB
Markdown
---
|
|
description: Commit current changes and push to the remote
|
|
---
|
|
|
|
Commit the current working-tree changes and push them.
|
|
|
|
1. Run `git status` and `git diff` to see what will be committed.
|
|
2. Check the current branch (`git branch --show-current`). If it's `main` and the
|
|
change looks feature-sized (not one of CLAUDE.md's "commit straight to main"
|
|
exceptions: small fixes, typos/formatting, or the user explicitly said `main`),
|
|
stop and tell the user to branch first — don't push a feature to `main`.
|
|
3. Stage the changed files (`git add -A` is fine here).
|
|
4. Create a commit with a short message describing the changes (infer it from the
|
|
diff), including the `Co-Authored-By: Claude <noreply@anthropic.com>` trailer.
|
|
Pass the message via a HEREDOC.
|
|
5. Push with `git push`. If the current branch has no upstream, use `git push -u origin HEAD`.
|
|
6. If the branch isn't `main`, remind the user to open an MR with `tea pr create`
|
|
(see CLAUDE.md's Branching & Merge Requests section) rather than opening one
|
|
automatically.
|
|
7. Report the commit hash and push result.
|
|
|
|
If there are no changes, stop and say so — do not create an empty commit.
|