Added some details on how to solve a `configure-pages` permission problem.

[Hamza5]

Why:

Closes: https://github.com/actions/starter-workflows/issues/332

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

There were no details in the documentation about the problem that happens when trying to use configure-pages without arguments. The default GITHUB_TOKEN does not have the required permission to make it work. I added some information to explain how to solve this problem because it happened to me and I solved it.

Check off the following:

• [x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• [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
pages/getting-started-with-github-pages/using-custom-workflows-with-github-pages.md	fpt ghec ghes@ 3.11 3.10 3.9 3.8 3.7	fpt ghec ghes@ 3.11 3.10 3.9 3.8 3.7

---

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

[nguyenalex836]

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

[nguyenalex836]

@Hamza5 Hello! 👋 Thank you for your patience while our team reviewed this PR! After speaking with our engineering team, they informed us you wouldn't actually need a personal access token in this instance.

You would just need to customize the permissions for the GITHUB_TOKEN. We appreciate your willingness to contribute to GitHub Docs! I'll go ahead and close this issue 💛