Specify scope for GITHUB_TOKEN about action-wordpress-plugin-deploy HOT 5 CLOSED

Thanks for your reply Jeff! I tried to run 'Upload release asset' on an 'add tag' action. This combination doesn't seem to work (probably because no release exists?). The deploy on a published release works perfectly, without the need to create a GitHub token.

from action-wordpress-plugin-deploy.

@marijnbent note that I proposed an update to our docs in #63, let me know if that seems to help better call out requirements related to what you were trying to do... thanks!

from action-wordpress-plugin-deploy.

Perfect Jeff! Congrats on the whitehouse.gov site btw 🤓

from action-wordpress-plugin-deploy.

When trying to create a GITHUB_TOKEN secret, I get the message this name is not allowed. Is it correct that you should not set this value @helen?

from action-wordpress-plugin-deploy.

@marijnbent its been a bit since I've had to set this up from scratch, but I don't believe you need to create a Personal Access Token and GITHUB_TOKEN doesn't need to be set up / configured. As long as you've configured:

• build steps for your plugin
• SVN password + username as org/repo secrets
• SLUG param if yours is different than the repo name
• ASSETS_DIR if yours aren't in .wordpress-org
• .distignore / .gitattributes for files to skip on deploy

Setting up ^ those items should be all that's needed. Let us know if you've done that and are NOT seeing the action deploy properly.

from action-wordpress-plugin-deploy.