Updating ghcr_token to github_token

[joshjohanning]

Why:

I think the ${{ secrets.ghcr_token }} is outdated, or at least not optimal. This assumes that you have a secret called ghcr_token and it doesn't specify you to create one.

It looks like this part of the doc was updated in Nov 2020 but since then, you can use the ${{ secrets.github_token }} to auth containers to GitHub Packages / GitHub Container Registry.

The ${{ secrets.github_token }} has write access to packages by default so this should work (and I have tested in my repo).

docker/docker.github.io updated their docs in June 2021; see:

• Issue: Authentication to GHCR is now possible via GITHUB_TOKEN docker/docs#13037
• PR: https://github.com/docker/docker.github.io/pull/13710/files#diff-81899a5ea558f3ffe7dbfdc1257ff448d8757d7274fea7aab20e0132bfe3d4b0R215

What's being changed:

This changes ${{ secrets.ghcr_token }} to ${{ secrets.github_token }} in the jobs.<job_id>.container.credentials and jobs.<job_id>.services.<service_id>.credentials sections in the "Workflow syntax for GitHub Actions" page.

Check off the following:

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

Writer impact (This section is for GitHub staff members only):

• This pull request impacts the contribution experience
  • I have added the 'writer impact' label
  • I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

[github-actions]

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	Staging	Production	What Changed
content/actions/using-workflows/workflow-syntax-for-github-actions.md	Modified	Original

[ramyaparimi]

@joshjohanning
Thanks so much for opening a PR! I'll get this triaged for review ⚡

[lecoursen]

Thanks! I'll merge this now. ⚡

[github-actions]

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 ⚡