-
Notifications
You must be signed in to change notification settings - Fork 60.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update managing-complex-workflows.md #762
Conversation
Environment variable names are apparently case-sensitive since without this change, the `example-command` (I tried it with `echo`) is fed the empty string. (On the other hand, environment variable names are case-_insensitive_ in one respect: Trying to define two environment variables whose names differ only in case yields a "duplicate definition" error.)
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Thanks for opening a PR @gsrohde! I'll get this triaged for review 🌟 |
Thanks a lot for this, @gsrohde! You are correct for most *nix OSs, but it might depend on the OS and shell of the runner executing the job. This example doesn't specify a |
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. |
Environment variable names are apparently case-sensitive since without this change, the
example-command
(I tried it withecho
) is fed the empty string. (On the other hand, environment variable names are case-insensitive in one respect: Trying to define two environment variables whose names differ only in case yields a "duplicate definition" error.) This relates to issue #761.Why:
The example does not work as expected.
What's being changed:
Check off the following: