Fixes breaking `base64` command options change in OSX 13.0+

[mikemike396]

Why:

OSX 13.0+ now requires the base64 command to pass the output file in one the following 2 formats. (https://www.unix.com/man-page/osx/1/base64/)

-o output_file
--output=output_file

What's being changed (if available, include any code snippets, screenshots, or gifs):

This command works in OSX 12 but not in 13:

echo -n "$BUILD_CERTIFICATE_BASE64" | base64 --decode --output $CERTIFICATE_PATH

Pipeline throws error: base64: invalid argument --output

This works in both:

echo -n "$BUILD_CERTIFICATE_BASE64" | base64 --decode -o $CERTIFICATE_PATH

Check off the following:

• [x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
• [x] For content changes, I have completed the self-review checklist.

[welcome[bot]]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions[bot]]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md	fpt ghec ghes@ 3.7 3.6 3.5 3.4 3.3 ghae	fpt ghec ghes@ 3.7 3.6 3.5 3.4 3.3 ghae

---

fpt: Free, Pro, Team ghec: GitHub Enterprise Cloud ghes: GitHub Enterprise Server ghae: GitHub AE

[cmwilson21]

@mikemike396 Thanks so much for opening a PR! I'll get this triaged for review :zap:

[Amirdarabi1377]

Why:

OSX 13.0+ now requires the base64 command to pass the output file in one the following 2 formats. (https://www.unix.com/man-page/osx/1/base64/)

-o output_file
--output=output_file

What's being changed (if available, include any code snippets, screenshots, or gifs):

This command works in OSX 12 but not in 13:

echo -n "$BUILD_CERTIFICATE_BASE64" | base64 --decode --output $CERTIFICATE_PATH

Pipeline throws error: base64: invalid argument --output

This works in both:

echo -n "$BUILD_CERTIFICATE_BASE64" | base64 --decode -o $CERTIFICATE_PATH

Check off the following:

• [x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
• [x] For content changes, I have completed the self-review checklist.

[github-actions[bot]]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues :zap: