Record MR creation in plan execution summary
Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -4,7 +4,7 @@ Plan: `docs/plans/2026-08-11-1935-gitea-build-workflow.md`
|
|||||||
|
|
||||||
- [x] Step 1 — Create `.gitea/workflows/build.yaml`
|
- [x] Step 1 — Create `.gitea/workflows/build.yaml`
|
||||||
- [x] Step 2 — Replace CLAUDE.md CI TODO with a CI/CD subsection
|
- [x] Step 2 — Replace CLAUDE.md CI TODO with a CI/CD subsection
|
||||||
- [ ] Step 3 — Push branch + open MR
|
- [x] Step 3 — Push branch + open MR
|
||||||
- [ ] Step 4 — CHANGELOG entry (after the first successful run is confirmed)
|
- [ ] Step 4 — CHANGELOG entry (after the first successful run is confirmed)
|
||||||
|
|
||||||
## Steps 1–2 — workflow + CLAUDE.md
|
## Steps 1–2 — workflow + CLAUDE.md
|
||||||
@@ -34,6 +34,17 @@ ruby -ryaml -e "YAML.load_file('.gitea/workflows/build.yaml'); puts 'YAML OK'"
|
|||||||
go vet ./... && go build ./... && go test -short ./... # all packages ok
|
go vet ./... && go build ./... && go test -short ./... # all packages ok
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## Step 3 — push + MR
|
||||||
|
|
||||||
|
Branch pushed and MR opened with `tea` (the worktree was then removed and the main
|
||||||
|
checkout switched onto the branch so the files are visible locally):
|
||||||
|
|
||||||
|
```bash
|
||||||
|
tea pr create --title "Add Gitea Actions image-build workflow" \
|
||||||
|
--description "..." --base main --head feat/gitea-build-workflow
|
||||||
|
# → https://gitea.home.hrajfrisbee.cz/kacerr/egress-proxies-operator/pulls/2
|
||||||
|
```
|
||||||
|
|
||||||
Worth noting: the workflow itself cannot run end-to-end until (a) the MR merges
|
Worth noting: the workflow itself cannot run end-to-end until (a) the MR merges
|
||||||
(it only triggers on tags / manual dispatch, not branch pushes) and (b) the
|
(it only triggers on tags / manual dispatch, not branch pushes) and (b) the
|
||||||
`REGISTRY_TOKEN` secret is created in this repo's Gitea settings (PAT with
|
`REGISTRY_TOKEN` secret is created in this repo's Gitea settings (PAT with
|
||||||
|
|||||||
Reference in New Issue
Block a user