CI/CD Pipeline

All pipelines live in kardistrey/progrista-cicd as reusable workflows — click a phase to focus, hover nodes for details

Architecture

Each repo keeps only its triggers; the jobs come from progrista-cicd@v1. Move the tag to roll out a change.

App repos · caller stubs Shared repo Reusable workflows progrista-ui ci · version-bump · deploy-pages live progrista-axis ci · version-bump pending rollout progrista-meta ci · version-bump pending rollout progrista-cicd tag v1 node-ci.yml python-ci.yml docker-publish.yml release-bump.yml pages-deploy.yml uses: …@v1 on: workflow_call

Release flow

Branching, CI and release are the same for every repo. Shown here for progrista-ui, the first repo on @v1.

Branching CI Checks Release, Deploy & Sync feature/** dev integration branch hotfix urgent fixes main production dependabot/* PR merge PR merge minor bump PR merge patch bump patch bump ci / lint ci / typecheck ci / test ci / format on push & PR ci.yml → node-ci.yml@v1 ci / gitleaks ci / build PRs to main only needs: all 5 deploy-pages.yml → pages-deploy.yml@v1 GitHub Pages ui.progrista.com push to main build + deploy docker-publish.yml@v1 axis · meta → ghcr.io after CI, main only version-bump.yml → release-bump.yml@v1 npm publish GH Release bump dev next minor bump hotfix next patch PR merged to main then
Branches
CI
Release
Sync