ci: Add Gitea Actions for the Go module #7

New Issue

2026-09-01T14:44:23-05:00

Ghost commented

2026-09-01 14:44:23 -05:00

Goal

Add Gitea Actions CI for this Go module and require the checks on master and develop, matching other forge Go modules.

Stack

Module: s1d3sw1ped/robinhood-agentic-mcp
Go from go.mod (currently 1.25.0) — use go-version-file: go.mod
Makefile already has test (go test ./...) and vet (go vet ./...)
Existing unit tests under package dirs; prefer go test -race ./... like other forge Go modules

Do

Add .gitea/workflows/ci.yaml (or ci.yml) modeled on existing forge Go CI:
- on: push to master and develop, plus pull_request
- Job name that will become the required status context (keep it stable; use job ci / "Test and build")
- checkout@v4, setup-go@v5 with go-version-file + cache
- go test -race ./...
- go build ./... (and/or make vet if useful; do not invent live Robinhood network calls)
No secrets, no lab SSH, no real OAuth against Robinhood in CI.
After CI is green once on the PR, Require the status check on branch protection for master and develop. You do not need to edit protection yourself unless the maintainer asks.
PR against develop (dual-branch). Do not merge yourself.
Commit style: forge git-style.md — ci: Add Gitea Actions workflow (or similar). PR title matches. Prefer full URL if citing this issue in leftover text; Fixes #N only if this issue is fully done.

Out of scope

Leak scrub / README rewrite (separate docs pass)
LICENSE
Publishing binaries / goreleaser unless already present
Hitting Robinhood production

Revert

git revert the CI commit / close the PR. No data migrations.

## Goal Add Gitea Actions CI for this Go module and require the checks on `master` and `develop`, matching other forge Go modules. ## Stack - Module: `s1d3sw1ped/robinhood-agentic-mcp` - Go from `go.mod` (currently 1.25.0) — use `go-version-file: go.mod` - Makefile already has `test` (`go test ./...`) and `vet` (`go vet ./...`) - Existing unit tests under package dirs; prefer `go test -race ./...` like other forge Go modules ## Do 1. Add `.gitea/workflows/ci.yaml` (or `ci.yml`) modeled on existing forge Go CI: - `on: push` to `master` and `develop`, plus `pull_request` - Job name that will become the required status context (keep it stable; use job `ci` / "Test and build") - checkout@v4, setup-go@v5 with go-version-file + cache - `go test -race ./...` - `go build ./...` (and/or `make vet` if useful; do not invent live Robinhood network calls) 2. No secrets, no lab SSH, no real OAuth against Robinhood in CI. 3. After CI is green once on the PR, Require the status check on branch protection for `master` and `develop`. You do not need to edit protection yourself unless the maintainer asks. 4. PR against `develop` (dual-branch). Do not merge yourself. 5. Commit style: forge `git-style.md` — `ci: Add Gitea Actions workflow` (or similar). PR title matches. Prefer full URL if citing this issue in leftover text; `Fixes #N` only if this issue is fully done. ## Out of scope - Leak scrub / README rewrite (separate docs pass) - LICENSE - Publishing binaries / goreleaser unless already present - Hitting Robinhood production ## Revert `git revert` the CI commit / close the PR. No data migrations.

Ghost referenced a pull request that will close this issue

2026-09-01 14:45:24 -05:00

ci: Add Gitea Actions workflow #10

Ghost referenced this issue from a commit

2026-09-01 14:45:25 -05:00

ci: Add Gitea Actions workflow

Ghost closed this issue

2026-09-01 14:46:22 -05:00

Sign in to join this conversation.