Add GitHub Actions CI workflow #5

New issue

Closed

opened 2026-09-20 15:04:55 +00:00 by agent · 0 comments

agent commented

2026-09-20 15:04:55 +00:00

Member

Problem

No CI automation exists. The README lists go vet ./... as a validation step but it's not automated. For a public library, automated verification is expected.

Plan

Create .github/workflows/ci.yml with:

name: CI
on: [push, pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-go@v5
        with:
          go-version: '1.25'
      - run: go build ./...
      - run: go vet ./...
      - run: go test -count=1 -race ./...

Optional: add golangci-lint job if the user wants stricter linting.

Notes

User plans to move this repo to github.com/Merith-TK/reconf at v1.0.0, so GitHub Actions is the correct CI system.
Keep it simple: build, vet, test with race detector.
The cmd/ packages have no tests — they will be ? (no test files), which is fine.

Verification

Push to a branch, confirm the workflow runs and passes.

## Problem No CI automation exists. The README lists `go vet ./...` as a validation step but it's not automated. For a public library, automated verification is expected. ## Plan Create `.github/workflows/ci.yml` with: ```yaml name: CI on: [push, pull_request] jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-go@v5 with: go-version: '1.25' - run: go build ./... - run: go vet ./... - run: go test -count=1 -race ./... ``` Optional: add golangci-lint job if the user wants stricter linting. ## Notes - User plans to move this repo to `github.com/Merith-TK/reconf` at v1.0.0, so GitHub Actions is the correct CI system. - Keep it simple: build, vet, test with race detector. - The `cmd/` packages have no tests — they will be `?` (no test files), which is fine. ## Verification Push to a branch, confirm the workflow runs and passes.

agent added the

proj-config-lib

tier-1-easy

labels

2026-09-20 15:05:49 +00:00

agent referenced this issue

2026-09-20 15:06:03 +00:00

Plan: Fix config library issues (priority order) #3

agent referenced this issue

2026-09-20 15:33:52 +00:00

Plan: Production readiness — v0.1.0 release blockers #11

agent closed this issue