chore(docs): Update explanation for token input - #125
Conversation
|
Hi, thanks for the PR! Just a quick question: are you sure it's necessary to use it in |
|
Yes, it took a while to realize that the token for this action isn't really necessary since it isn't used for the git actions. For the workflows it's important who made the commit and if it's from the default GitHub token no other workflows are triggered. |
|
Oh ok I get it: the token that the |
|
Sorry, I was just thinking: if it's the repo token (which is set by |
|
I'm not sure if there are environments where the default token doesn't exist/has no repo access. Since it's already optional I don't see any harm in keeping it. We could also update the comment to "and optionally here" as long as we say that it's not the one used for commits.
Correct, that's also documented here. |
|
I've moved the token info to a new paragraph, what do you think? |
|
@EndBug Looks good to me! |
|
@all-contributors please add @ocean90 for docs |
|
I've put up a pull request to add @ocean90! 🎉 |
The token input is actually not used for pushing the commit. It's only used for fetching author data from the API.
To trigger other workflows the token needs to be added to the
actions/checkoutstep because that auth will be used for the git commands of this action. This PR tries to clarify this a bit more.