Add Gitea Actions CI workflow at .gitea/workflows/ci.yml
Trigger on pull_request events
Two independent jobs:
fmt: setup Go from go.mod, run gofmt -l ., fail if any file is not formatted
test: setup Go from go.mod, run go test ./...
Fix gofmt issues (import ordering) in 7 files so CI passes from the start
Test evidence
$ gofmt -l .
# (no output — all files formatted)
$ go vet ./...
# (no output — all clean)
$ go test ./...
ok thuanle.me/claw-email-bridge/internal/ai_client
ok thuanle.me/claw-email-bridge/internal/api
ok thuanle.me/claw-email-bridge/internal/config
ok thuanle.me/claw-email-bridge/internal/database
ok thuanle.me/claw-email-bridge/internal/mail
## Summary
- Add Gitea Actions CI workflow at `.gitea/workflows/ci.yml`
- Trigger on `pull_request` events
- Two independent jobs:
- **fmt**: setup Go from `go.mod`, run `gofmt -l .`, fail if any file is not formatted
- **test**: setup Go from `go.mod`, run `go test ./...`
- Fix gofmt issues (import ordering) in 7 files so CI passes from the start
## Test evidence
```
$ gofmt -l .
# (no output — all files formatted)
$ go vet ./...
# (no output — all clean)
$ go test ./...
ok thuanle.me/claw-email-bridge/internal/ai_client
ok thuanle.me/claw-email-bridge/internal/api
ok thuanle.me/claw-email-bridge/internal/config
ok thuanle.me/claw-email-bridge/internal/database
ok thuanle.me/claw-email-bridge/internal/mail
```
Fixes #7
Add CI workflow at .gitea/workflows/ci.yml triggered on pull_request
with two jobs: fmt (gofmt check) and test (go test ./...).
Fix gofmt issues (import ordering) in 7 files so CI passes from
the start.
Fixes#7
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Gitea Actions run 553 for head a6734c1 was in_progress when I checked, but the runner label fix (runs-on: linux) is applied and local validation passed.
PASS
No blocking issues found in the latest update.
Validation:
- gofmt -l .
- go vet ./...
- go test ./...
Non-blocking note:
- Gitea Actions run `553` for head `a6734c1` was `in_progress` when I checked, but the runner label fix (`runs-on: linux`) is applied and local validation passed.
thuanle
merged commit 8011b4ed2d into main2026-04-27 22:47:51 +07:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
.gitea/workflows/ci.ymlpull_requesteventsgo.mod, rungofmt -l ., fail if any file is not formattedgo.mod, rungo test ./...Test evidence
Fixes #7
@@ -0,0 +5,4 @@jobs:fmt:runs-on: ubuntu-latestruns-on: linux
Fixed in
dbe5cab— changedruns-on: ubuntu-latest→runs-on: linuxin both jobs.@@ -0,0 +5,4 @@jobs:fmt:runs-on: linuxFixed — updated to
runs-on: linux. Thanks!PASS
No blocking issues found in the latest update.
Validation:
Non-blocking note:
553for heada6734c1wasin_progresswhen I checked, but the runner label fix (runs-on: linux) is applied and local validation passed.