In this chapter, we introduced a new concept and method of managing code signing, using a collective code sharing workflow that replaces the silos of development certificates and provisioning profiles that individual developers use (as we have relied on in the previous chapters) with a singular code signing certificate, private key, and profile that is stored in a private Git repository and shared among the development team.
match (https://docs.fastlane.tools/actions/match#readme) has allowed us to deprecate calling sigh and cert explicitly in our lane in lieu of this one command that not only manages the entire code signing set of assets but encrypts and synchronizes the assets into the Git repository automatically, meaning that onboarding new developers is extremely effortless.
In the next chapter, we are going to complete the first block of chapters that focus...