The runner standard is canonical in pla-stack:

How to replicate GitLab's when: manual deploy behavior in GitHub Actions using environment protection rules. This pattern gives developers an approval button visible in the PR checks, similar to GitLab's inline manual deploy button.

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.

Repositories that follow the feature/ → dev → main workflow enforce merge commit only* when a PR is merged into main. Squash and rebase merges are disabled for that target.

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 34 active GitLab repositories in the publicala group, organized by migration priority. Archived repos (76) are excluded; GitLab remains as reference for those. Data sourced from GitLab API and local repository inspection.