-
I have an action that needs to generate a UWP package. Things worked fine when my commands were plain and didn’t use any environment variables. I.e.:
Now, in an effort to make this action more generic, I’ve done:
Then:
When doing that, I get an error about the “/p” option not being recognized. I suspect a command line parsing bug where perhaps a missing parameter reports as an unknown option, so I do:
after generating package.appx. As suspected, Interestingly, I have:
earlier in my action, and it works just fine. So there’s something with my use of What am I doing wrong here? This is probably more of a generic PowerShell issue, but it seems like I’m using environment variables correctly, and I can’t find the right Google keywords to fix this. Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi, I’m not sure what exactly is causing your issue, but can you try this syntax instead and see if it works:
This lets GitHub interpolate the env for you |
Beta Was this translation helpful? Give feedback.
-
Doh, didn’t even think about that. Yeah, that seems to have fixed it. |
Beta Was this translation helpful? Give feedback.
Hi,
I’m not sure what exactly is causing your issue, but can you try this syntax instead and see if it works:
This lets GitHub interpolate the env for you