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
Prompted variables have their values supplied at deployment time, and not at release creation. However you can use the --variable=VALUE parameter in Octo.exe's create-release command, which will supply the value if you also have the --deployto parameter set in the same command. If you use the --variable option without the --deployto option, no error or warning is displayed, which it should.
Additionally, we should probably update the octo.exe help text to make this more clear. Currently it says
[Optional] Values for any prompted variables in the format Label:Value. For JSON values, embedded quotation marks should be escaped with a backslash.
Prompted variables have their values supplied at deployment time, and not at release creation. However you can use the --variable=VALUE parameter in Octo.exe's create-release command, which will supply the value if you also have the --deployto parameter set in the same command. If you use the --variable option without the --deployto option, no error or warning is displayed, which it should.
Additionally, we should probably update the octo.exe help text to make this more clear. Currently it says
One example of this common confusion that this change could have potentially prevented: https://secure.helpscout.net/conversation/904123519/47238?folderId=954335 (private link)
The text was updated successfully, but these errors were encountered: