Skip to content

chore: sync agent skills from frostyard/core #209

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bketelsen wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: sync agent skills from frostyard/core #209

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 20 additions & 5 deletions docs/agents/skills/frostyard-go-repo/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,10 +71,25 @@ Rules:
- `test.yml` — jobs: golangci-lint, govulncheck, unit tests with Codecov
OIDC upload, e2e tests, `-race`, verify (`go mod tidy` diff, `go vet`,
`gofmt -l`), and a linux amd64/arm64 build matrix. Pin actions by SHA.
- `release.yml` — on tag push: GoReleaser Pro (`distribution:
goreleaser-pro`, needs `secrets.GORELEASER_KEY`) then publish packages
to the org apt/rpm repo via `frostyard/repogen`'s `publish-to-r2`
action (needs the `R2_*` secrets).
- `release.yml` — on tag push, three steps:
1. GoReleaser Pro (`distribution: goreleaser-pro`, needs
`secrets.GORELEASER_KEY`).
2. `actions/attest-build-provenance` over `dist/checksums.txt` and the
packages; the job grants `id-token: write` and
`attestations: write`.
3. A `publish-deb` `repository_dispatch` to `frostyard/apt-publisher`
with `repo` and `tag`, using `secrets.APT_PUBLISH_TOKEN`. Don't
guard it, and don't mark it `continue-on-error`.

apt-publisher publishes the `.deb` files to
`https://repository.frostyard.org/debian/`, then dispatches `build`
to the image repos
([core ADR-0055](https://github.com/frostyard/core/blob/main/docs/adr/0055-publish-debian-packages-through-the-apt-publisher.md),
[ADR-0056](https://github.com/frostyard/core/blob/main/docs/adr/0056-rebuild-images-after-apt-publication.md)).
So the repo holds no signing or R2 credentials, and doesn't dispatch
`build` itself. Before the first release:
- register the repo in apt-publisher's `config/producers.tsv`;
- share the org `APT_PUBLISH_TOKEN` secret with it.
- `snapshot.yml` — nightly GoReleaser `release --nightly --clean` under
the `dev` tag after green `main` tests. Use this exact top-level block:

Expand Down Expand Up @@ -107,7 +122,7 @@ Rules:
- GoReleaser config is **Pro** (`pro: true`); running it with the OSS
distribution fails. CI needs `GORELEASER_KEY`.
- The nfpm package name is `frostyard-<name>`, not `<name>` — keep that
prefix so org packages sort together in the apt/rpm repo.
prefix so org packages sort together in the APT repository.
- `make lint` silently skips if golangci-lint isn't installed — CI is the
backstop, so don't treat a quiet local `make check` as proof lint ran.
- Don't disable the snapshot workflow's `cancel-in-progress` — see step 3.
Loading