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.

The runner standard is canonical in pla-stack:

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).

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.

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.

We are migrating all source code repositories from GitLab (publicala group) to GitHub (publicala org, Enterprise plan). This document covers motivation, scope, approach, and current state.

Step-by-step checklist for migrating repositories from GitLab to GitHub. Each repo follows the same per-repo process; cross-cutting tasks are handled once after all repos are moved.

Catalog of 33 active GitLab repositories in the publicala group, organized by migration priority. Archived repos (77) are excluded; GitLab remains as reference for those. Data sourced from GitLab API and local repository inspection.