-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
GITHUB_*
variables are empty
#2418
Comments
..........
Those are empty as run is not an action, please check this against actions/runner
act pull_request exclusive if Do you have some suggestion to get the values? I believe we have documented how the event.json must look like, but that could be invalid didn't verify
What is expected here for refs/pull ? I remember that was undefined while the code has been written and empty was correct |
Yeah, that makes sense. For now, I don't care about these anyways.
What do you mean by this (
We can gather these independent of Github, since we know the base branch, and the current branch. We can set
From the docs, though, I've never used it myself or seen it used 🤷
|
Yes, that is for refs/tag/ and refs/heads/, but we are writing about refs/pull/.
The trigger event name is checked: act/pkg/model/github_context.go Line 203 in bda491e
act push never set's the value from event.json, but I think you don't provide such a file. To set the value currently just do
Line 880 in bda491e
I don't know it, I would need to guess it. A sha might be an unexpected value here Not every PR goes to default branch, only most. As a default fallback it's ok, you can make a pr, but please only for events contain pull_request in their name
As a default fallback it's ok, you can make a pr, but please only for events contain pull_request in their name |
Bug report info
Command used with act
Describe issue
Some
GITHUB_*_REF
variables are empty, even though Act claims on its front page to provide these variables.These are empty:
Link to GitHub repository
https://github.com/AndesKrrrrrrrrrrr/act-MWE/tree/main
Workflow content
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: