DOC Update

[sjrulandch]

For the GHP example, it would have been nice to have the following mentioned:

permissions:
  packages: write

[priyagupta108]

Hi @sjrulandch 👋,
Thank you for reporting this! We will look into it and get back to you as soon as we have updates.

[priya-kinthali]

Hello @sjrulandch👋,

Thank you for the suggestion!
The permissions key is used to modify the default permissions granted to the GITHUB_TOKEN. You can refer to the following GitHub official documentation links for more details:

• Configuring the default GITHUB_TOKEN permissions: This section details the repository settings under "Workflow permissions," where you can choose whether you want the GITHUB_TOKEN to have read and write access for all permissions (the permissive setting), or just read access for the contents and packages permissions (the restricted setting).
• Automatic token authentication - Permissions for the GITHUB_TOKEN: This section details the default permissions granted to the GITHUB_TOKEN and how users with admin permissions can set the default permissions.
• Workflow syntax for GitHub Actions - Permissions: This section explains how to modify the default permissions granted to the GITHUB_TOKEN within your workflow file.
• Publish NuGet packages to GitHub Packages: This documentation provides comprehensive instructions on publishing NuGet packages, including setting the necessary permissions.

We feel it may not be necessary to include permissions: packages: write in the example for the setup-dotnet action, as specifying this depends on the individual repository settings related to the default permissions granted to the GITHUB_TOKEN and the specific project requirements.
Hope this clarifies. Please let us know in case of any further concerns.
Thank you!