Skip to content

Commit fa39abd

Browse files
authored
Add GITHUB_TOKEN instructions to tip admonition
1 parent 35dbd1e commit fa39abd

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -169,8 +169,11 @@ Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_
169169
to sign the distribution packages. In the next step, an empty GitHub Release
170170
from the current tag is created using the ``gh`` CLI. Note this step can be further
171171
customised. See the `gh release documentation <https://cli.github.com/manual/gh_release>`_
172-
as a reference. To enable writing to GitHub Release you may need to manage your ``GITHUB_TOKEN``
173-
permissions, see the `GitHub documentation <https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-default-github_token-permissions>`_.
172+
as a reference.
173+
174+
.. tip::
175+
176+
You may need to manage your ``GITHUB_TOKEN`` permissions to enable creating the GitHub Release. See the `GitHub documentation <https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-default-github_token-permissions>`_ for instructions. Specifically, the token needs `content.write` permissions.
174177

175178
Finally, the signed distributions are uploaded to the GitHub Release.
176179

0 commit comments

Comments
 (0)