Skip to content
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

Environment variables must be strings #16

Closed
DEGoodmanWilson opened this issue Jan 21, 2019 · 1 comment
Closed

Environment variables must be strings #16

DEGoodmanWilson opened this issue Jan 21, 2019 · 1 comment

Comments

@DEGoodmanWilson
Copy link

GitHub requires that all values to environment variables be strings—not, for example, integers. Act will heppily accept integers, however.

Here is an example workflow that act will execute, but that GitHub will reject:

workflow "Launch the rescue mission" {
  on = "release"
  resolves = ["debug"]
}

action "debug" {
  uses = "actions/bin/debug"
  env = {
    ENV_VAR = 1
    }
}

GitHub, on the other hand, requires something like

workflow "Launch the rescue mission" {
  on = "release"
  resolves = ["debug"]
}

action "debug" {
  uses = "actions/bin/debug"
  env = {
    ENV_VAR = "1"
    }
}

(notice the "1" in quotes)

@DEGoodmanWilson
Copy link
Author

(BTW, thank you for this very awesome tool!)

@cplee cplee closed this as completed in #27 Feb 7, 2019
makrsmark pushed a commit to makrsmark/act that referenced this issue Aug 3, 2023
Fix nektos#15.

Reviewed-on: https://gitea.com/gitea/act/pulls/16
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: Jason Song <i@wolfogre.com>
Co-committed-by: Jason Song <i@wolfogre.com>
makrsmark pushed a commit to makrsmark/act that referenced this issue Aug 3, 2023
makrsmark pushed a commit to makrsmark/act that referenced this issue Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant