Repository navigation
Keep the certificate store on one branch - #26
Merged
Merged
Conversation
match writes to "master" unless told otherwise, so a certs repo created today — default branch main — ends up with the certificate on master and an empty main. Pin git_branch so a fresh store bootstraps onto the branch the repo uses.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fastlane
matchwrites to amasterbranch unless told otherwise, but a GitHub repo created today defaults tomain. A store bootstrapped throughios-ci inittherefore ended up split: the certificate and profile onmaster, an emptymain.Pins
git_branch: "main"in the lane so a fresh store lands on the branch the repo actually uses, and says so in the skill and the docs. An existingmaster-based store needs its content merged intomainonce.Matches KAppMaker/KAppMaker-All#7. Bumps to 1.24.1 / plugin 2.10.1.