Skip to main content

6 docs tagged with "ci-cd"

View all tags

Branch Strategy

Publica.la's standard for all GitHub-hosted repos: trunk-based development on main. No dev branch. No develop branch. One long-lived integration branch, period.

CI/CD Translation Reference

Mapping GitLab CI concepts and patterns to GitHub Actions equivalents. Use alongside gh actions-importer for automated translation, then review and adjust using this reference.

Deploy Approval Pattern

How we replicate GitLab's when the split-gate pattern (a tiny approval job plus a deploy job), the concurrency rules, and the two variants (Laravel Cloud, Laravel Vapor).

Dropping the dev Branch

Per-repo runbook for cutting over a dev + main repo to trunk-based (main only). Follow this in order. Do not skip steps. The rationale is in Branch Strategy.

GitHub Actions Pinning Policy

Every uses: entry in every GitHub Actions workflow across the publicala organization must be pinned to a specific version. This policy defines how to pin, what to pin to, and how to handle future deprecations without accumulating backlogs.

Runners Setup

We use Cloud Runner for our GitLab CI/CD runners. They provide fully managed runners so we don't have to maintain our own infrastructure.

X

Graph View