Ninosaurier/LUNA-Charts
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Configure CI/CD pipeline #10

New Issue
Closed
opened 2026-07-22 21:20:17 +00:00 by Ninosaurier · 0 comments
Ninosaurier commented 2026-07-22 21:20:17 +00:00
Owner
Copy Link
Copy Source

Context

Local test and lint commands exist, but nothing currently runs them automatically on push or Pull Request. Without CI, there's no enforced quality gate — a contributor (or the maintainer) could merge a change that fails lint or tests without noticing.

Goal

  • Add a Gitea Actions (or GitHub Actions, for the mirrored repo) workflow that runs on every push and Pull Request to main
  • Pipeline should run: pnpm lint, pnpm test:unit, and pnpm test:component (using the existing Docker-based Playwright setup)
  • Merges to main should be blocked if the pipeline fails (tie into branch protection, see CONTRIBUTING.md)

Why this matters

  • Automated testing is defined as a blocking release gate in the Technology Architecture (Section 6) — without CI, this policy exists only on paper
  • This is also the last remaining open item of the Foundation milestone

Related

  • docs/.../architecture/adm/technology-architecture.mdx (Release Gate Policy)
  • CONTRIBUTING.md
## Context Local test and lint commands exist, but nothing currently runs them automatically on push or Pull Request. Without CI, there's no enforced quality gate — a contributor (or the maintainer) could merge a change that fails lint or tests without noticing. ## Goal - Add a Gitea Actions (or GitHub Actions, for the mirrored repo) workflow that runs on every push and Pull Request to `main` - Pipeline should run: `pnpm lint`, `pnpm test:unit`, and `pnpm test:component` (using the existing Docker-based Playwright setup) - Merges to `main` should be blocked if the pipeline fails (tie into branch protection, see CONTRIBUTING.md) ## Why this matters - Automated testing is defined as a **blocking release gate** in the Technology Architecture (Section 6) — without CI, this policy exists only on paper - This is also the last remaining open item of the Foundation milestone ## Related - `docs/.../architecture/adm/technology-architecture.mdx` (Release Gate Policy) - `CONTRIBUTING.md`
Ninosaurier added this to the v0.2.0 - Phase 2: Foundation milestone 2026-07-22 21:20:17 +00:00
Ninosaurier added the Kind/TestingPriority/High labels 2026-07-22 21:20:17 +00:00
Ninosaurier self-assigned this 2026-07-22 21:20:17 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Community/Good First Issue
Suitable for newcomers making their first contribution.
 Community/Question
General questions or discussions without implementation work.
 Kind/Bug
Something is not working correctly.
 Kind/Documentation
Documentation changes or improvements.
 Kind/Enhancement
Improves existing functionality.
 Kind/Feature
Introduces new functionality.
 Kind/Refactoring
Improves internal implementation without changing external behavior.
 Kind/Testing
Related to tests or testing infrastructure.
 Priority/High
High priority.
 Priority/Low
Low priority.
 Priority/Medium
Normal priority.
 Status/Blocked
Progress is blocked by another dependency or issue.
 Status/Needs Information
More details or steps to reproduce are required from the author before proceeding.
 Status/Needs Review
Waiting for maintainer or reviewer feedback.
 Status/Verified
The issue has been verified and confirmed.
No labels Kind/Testing Priority/High
Milestone
No items
No Milestone v0.2.0 - Phase 2: Foundation
Projects
Clear projects
No projects
Assignees
Clear assignees
Ninosaurier (Antonino Provenzano)
No Assignees Ninosaurier
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Ninosaurier/LUNA-Charts#10