Adds a Feed post for the Data Controller customer story video.
content/feed/customer-story/index.md - the post, with the video embedded.
content/feed/customer-story/customer-story.jpeg - the cover.
The cover is a PLACEHOLDER composed locally; the real deliverable is the Image prompt comment in the post. Overwrite customer-story.jpeg with the generated art (1200x627), or say the word and I will drop the file instead.
Verified: clean rebuild, npm run typecheck, npm run lint (only the 8 pre-existing warn files, none of them touched).
Adds a Feed post for the Data Controller customer story video.
- `content/feed/customer-story/index.md` - the post, with the video embedded.
- `content/feed/customer-story/customer-story.jpeg` - the cover.
The cover is a PLACEHOLDER composed locally; the real deliverable is the `Image prompt` comment in the post. Overwrite `customer-story.jpeg` with the generated art (1200x627), or say the word and I will drop the file instead.
Verified: clean rebuild, `npm run typecheck`, `npm run lint` (only the 8 pre-existing warn files, none of them touched).
Reviewed the new feed post (content/feed/customer-story/index.md, cover jpeg) plus repo-level hardening (pre-commit hook, CI audit gate). No package.json or lockfile changes in this diff; no release tooling in this repo, so commit message format is not release-driving.
Missing gitleaks pre-commit hook: no .pre-commit-config.yaml at the repo root. Standing all-repo requirement - add one with a gitleaks hook (id: gitleaks) pinned to an exact release tag (current release v8.30.1). Re-flagged on every review until it lands.
No npm audit step in either publish workflow (.gitea/workflows/publish.yml, .github/workflows/publish.yml). Both run npm ci, then build and deploy with nothing that fails the build on a vulnerability. Add npm audit (default level, or --audit-level=low) as a gating step to at least one pipeline.
2 findings above for review.
Reviewed the new feed post (content/feed/customer-story/index.md, cover jpeg) plus repo-level hardening (pre-commit hook, CI audit gate). No package.json or lockfile changes in this diff; no release tooling in this repo, so commit message format is not release-driving.
- Missing gitleaks pre-commit hook: no .pre-commit-config.yaml at the repo root. Standing all-repo requirement - add one with a gitleaks hook (id: gitleaks) pinned to an exact release tag (current release v8.30.1). Re-flagged on every review until it lands.
- No npm audit step in either publish workflow (.gitea/workflows/publish.yml, .github/workflows/publish.yml). Both run npm ci, then build and deploy with nothing that fails the build on a vulnerability. Add npm audit (default level, or --audit-level=low) as a gating step to at least one pipeline.
2 findings above for review.
allan
merged commit cb072bf60a into main2026-10-11 10:30:20 +00:00
allan
deleted branch feed/customer-story2026-10-11 10:30:20 +00: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.
Adds a Feed post for the Data Controller customer story video.
content/feed/customer-story/index.md- the post, with the video embedded.content/feed/customer-story/customer-story.jpeg- the cover.The cover is a PLACEHOLDER composed locally; the real deliverable is the
Image promptcomment in the post. Overwritecustomer-story.jpegwith the generated art (1200x627), or say the word and I will drop the file instead.Verified: clean rebuild,
npm run typecheck,npm run lint(only the 8 pre-existing warn files, none of them touched).Reviewed the new feed post (content/feed/customer-story/index.md, cover jpeg) plus repo-level hardening (pre-commit hook, CI audit gate). No package.json or lockfile changes in this diff; no release tooling in this repo, so commit message format is not release-driving.
2 findings above for review.