You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 4, 2021. It is now read-only.
I am curious why the token 1) is taken as an environment variable instead of an input, and 2) not defaulted to ${{ github.token }}, which seems to be the idiom on most other actions, especially the official ones. If it's just for legacy/compatibility reasons, totally understandable. Just checking if I am missing something here and if there are some semantic differences that I am missing.
The text was updated successfully, but these errors were encountered:
Some workflows may require custom secrets different from ${{ github.token }}. For examples, releases created with ${{ github.token }} do not trigger any events, and if you want them to do so, you will need to provide a personal access token.
Sure. But taking that as an input that defaults to ${{ github.token }} would still allow for overriding it, and is how most other actions do it these days.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am curious why the token 1) is taken as an environment variable instead of an input, and 2) not defaulted to
${{ github.token }}
, which seems to be the idiom on most other actions, especially the official ones. If it's just for legacy/compatibility reasons, totally understandable. Just checking if I am missing something here and if there are some semantic differences that I am missing.The text was updated successfully, but these errors were encountered: