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
A clear and concise description of what the bug is. Include version by typing gh --version.
version:
Steps to reproduce the behavior
Create a file named .env (inside existing GitHub repo)
Add the following contents:
FOO="
Hello World
This fails to parse
"
run gh secret set -f .env
read "error parsing env file: Can't separate key from value"
Expected vs actual behavior
I found myself saving public and private keys (for better or worse!) in GitHub Actions Secrets. Because the gh CLI cannot parse line breaks I need to replace any linebreaks in the file with some other seperator eg. _ so that my variable can exist on a single line.
I don't know where the spec exists (if there is one) for .env files, however I do know that within Deno these variables with line breaks were parsed without issues, they just couldn't be uploaded to github in that format.
Logs
gh secret set -f .env
error parsing env file: Can't separate key from value
The text was updated successfully, but these errors were encountered:
@johnstonmatt Thank you for reporting and thank you @BakaFT for linking the relevant PR. Once this is fixed upstream we can pull in the updated godotenv version 👍
Describe the bug
A clear and concise description of what the bug is. Include version by typing
gh --version
.version:
Steps to reproduce the behavior
.env
(inside existing GitHub repo)gh secret set -f .env
"error parsing env file: Can't separate key from value"
Expected vs actual behavior
I found myself saving public and private keys (for better or worse!) in GitHub Actions Secrets. Because the
gh
CLI cannot parse line breaks I need to replace any linebreaks in the file with some other seperator eg._
so that my variable can exist on a single line.I don't know where the spec exists (if there is one) for
.env
files, however I do know that within Deno these variables with line breaks were parsed without issues, they just couldn't be uploaded to github in that format.Logs
The text was updated successfully, but these errors were encountered: