Add a copy-paste release.yml template #12

New issue

Closed

opened 2026-08-14 18:56:55 +00:00 by ahmad · 0 comments

ahmad commented

2026-08-14 18:56:55 +00:00

Owner

Context

New projects adopt the release flow by cribbing release.yml from an existing repo
(portfolio/imamah/launchpad). A documented skeleton in this repo makes that a copy,
fill placeholders, done — and keeps the canonical shape in one place.

Scope

In: templates/release.yml, the four-job flow (version → publish → deploy →
notify) wired to the shared actions, with <PLACEHOLDER>s for the app-specific
bits; a README pointer.
Out: a full project generator; the companion deploy.yml (noted, not shipped).

Acceptance criteria

Given a new project, when it copies templates/release.yml and fills the placeholders, then it has a working standard release pipeline off @v3.
The template parses as valid YAML and passes actionlint (bar the expected Forgejo full-URL notes).

### Context New projects adopt the release flow by cribbing `release.yml` from an existing repo (portfolio/imamah/launchpad). A documented skeleton in this repo makes that a copy, fill placeholders, done — and keeps the canonical shape in one place. ### Scope - In: `templates/release.yml`, the four-job flow (version → publish → deploy → notify) wired to the shared actions, with `<PLACEHOLDER>`s for the app-specific bits; a README pointer. - Out: a full project generator; the companion `deploy.yml` (noted, not shipped). ### Acceptance criteria - [ ] Given a new project, when it copies templates/release.yml and fills the placeholders, then it has a working standard release pipeline off `@v3`. - [ ] The template parses as valid YAML and passes actionlint (bar the expected Forgejo full-URL notes).

ahmad referenced this issue from a pull request that will close it,

2026-08-14 18:59:11 +00:00

docs: Add a release.yml template #13

ahmad closed this issue

2026-08-14 19:50:41 +00:00

ahmad referenced this issue from a commit

2026-08-14 19:50:42 +00:00

docs: Add a release.yml template (#13)