Skip to content

ci: gate & auto-merge automated emela version bumps - #5

Merged
Allianaab2m merged 1 commit into
mainfrom
ci/auto-merge-version-bumps
Jul 22, 2026
Merged

Allianaab2m merged 1 commit into
mainfrom
ci/auto-merge-version-bumps

Conversation

@Allianaab2m

Copy link
Copy Markdown
Member

What

  • New ci workflow (on: pull_request): runs nix flake check (eval-only) and builds the pinned release binary nix build .#emela on ubuntu-latest (x86_64-linux) and macos-latest (aarch64-darwin). A final aggregate ci job is the single status check to require.
  • update-emela-pin workflow: after opening the bump PR, runs gh pr merge --squash --auto so GitHub merges it automatically once ci passes.

Repo config applied alongside this PR

  • allow_auto_merge = true, delete_branch_on_merge = true
  • Branch protection on main: required status check ci, no required reviews, enforce_admins = false.

Why it works

Bump PRs are authored by the emela-release GitHub App, so ci triggers on them (a GITHUB_TOKEN-authored PR would not trigger workflows, and the required check would never appear). This PR itself exercises the new ci check end-to-end.

Add a pull_request CI workflow (nix flake check + build the pinned
emela binary on linux/darwin) and wire the update-emela-pin workflow to
enable native auto-merge on the PRs it opens. main now requires the ci
check, so bumps merge automatically only once that check is green.
@Allianaab2m
Allianaab2m merged commit eea016a into main Jul 22, 2026
3 checks passed
@Allianaab2m
Allianaab2m deleted the ci/auto-merge-version-bumps branch July 22, 2026 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant