laywill / laywill/laywill.github.io
Tag-gated release pipeline to GitHub Pages
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 0
- Forks
- 0
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 58
Description
Deploys happen only from v* tags. Release workflow: lint + SAST + build + link check as jobs; the deploy job needs: all of them. -rc pre-release tags run everything but skip the deploy step (pipeline dry-run). Artifact = built dist/ only, never the repo tree. Optionally restrict the github-pages environment to tag refs.
See architecture.md for the full pipeline diagram and rules.
Depends on: Astro scaffold, CI workflows.
Acceptance criteria
-
v2.0.0-rc.1tag runs the full pipeline green with deploy skipped - Deploy job provably requires all check jobs (
needs:) - No branch-push trigger can deploy
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/overhaul/architecture.md and the existing CI workflows, then inspect how the Astro scaffold produces dist/. Run the pipeline with a v2.0.0-rc.1 tag and verify lint, SAST, build, and link-check jobs complete while deploy is skipped; confirm deploy requires every check job and branch pushes cannot deploy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100