clawbot
93bbd80d57
check / check (push) Canceled after 0s
Completed Steps, the dated log of finished work, is removed. The Workflow says to delete Next Step once done instead of moving it there, and Status no longer names the first release candidate. The README's TODO section no longer says the file records what has been done. Model: opus-5-5
34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
# Workflow
|
|
|
|
- branch from `next`
|
|
- do the work in Next Step
|
|
- delete Next Step from `TODO.md`
|
|
- move the top item of Future Steps into Next Step
|
|
- commit (`TODO.md` changes in the same commit as the work)
|
|
- push the branch and open a PR against `next`
|
|
|
|
# Status
|
|
|
|
pre-1.0. Release candidates are tagged on `next`; `git tag --merged origin/next`
|
|
lists them. `main` is the stable branch and `next` the development branch, which
|
|
every PR targets. The frontend and the Go backend ship as one Docker image. The
|
|
Gitea workflow `.gitea/workflows/check.yml` runs `script/cibuild` on every push,
|
|
and cancels the older run on the same branch. Working toward 1.0.0.
|
|
|
|
# Next Step
|
|
|
|
Run `make frontend-viewport-test` in CI as its own step; it is not part of
|
|
`make check`, as it needs Docker and takes minutes.
|
|
|
|
# Future Steps
|
|
|
|
- A backend test that posts a report to `POST /api/v1/reports` and checks the
|
|
compressed file it is written to
|
|
- A backend route that decompresses the stored reports and answers queries on
|
|
them
|
|
- Prometheus metrics for the backend's in-memory buffer: its size, the number of
|
|
flushes and the number of reports
|
|
- A configurable host list (an environment variable or a config file)
|
|
- Export of the latency history (CSV or JSON)
|
|
- A notification when the health status changes to DEGRADED
|