Skip to content

Keep the certificate store on one branch - #7

Merged
mirzemehdi merged 1 commit into
mainfrom
fix/certs-branch-main
Aug 16, 2026
Merged

mirzemehdi merged 1 commit into
mainfrom
fix/certs-branch-main

Conversation

@mirzemehdi

Copy link
Copy Markdown

fastlane match writes to a master branch unless told otherwise, but a GitHub repo created today defaults to main. The result is a certificate store split across two branches — the certificate on master, an empty main — which is confusing at best and, if anything later reads the default branch, a build that cannot find its signing identity.

Pins git_branch: "main" so a fresh store bootstraps onto the branch the repo actually uses.

An existing store already on master needs its content merged into main once; after that, nothing changes.

@mirzemehdi
mirzemehdi force-pushed the fix/certs-branch-main branch from 0301d76 to b10e2f8 Compare August 16, 2026 19:12
match writes to "master" by default, so a certs repo created through the normal
GitHub flow ends up with the certificate on master and an empty main.
@mirzemehdi
mirzemehdi merged commit cba07f8 into main Aug 16, 2026
@mirzemehdi
mirzemehdi deleted the fix/certs-branch-main branch August 16, 2026 19:14
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