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
{{ message }}
Repository navigation
github.event_path cannot be passed through env var #701
Describe the bug
When passing ${{ github.event_path }} through as an environment variable, it ends up getting blanked out when trying to use the environment variable. The environment variable approach was previously working on v2.273.0, but appears to have broke in v2.273.1.
To Reproduce
Use the following workflow below.
name: event_path (manual trigger)
on:
workflow_dispatch:
jobs:
test:
runs-on: 'ubuntu-latest'
steps:
# - name: Printing through context works
# run: |
# echo ${{ github.event_path }}
- name: Printing through env var does not
run: |
echo $EVENT_PATH
env:
EVENT_PATH: ${{ github.event_path }}
Expected behavior
The value of ${{ github.event_path }} should be accessible as an environment variable.
Runner Version and Platform
Version of your runner? v2.273.1
OS of the machine running the runner? ubuntu-latest
Since this does not happen on newer verions of runner, I will close this issue. Feel free to reopen it if the problem still exists or you have more questions.
Okay, now it's clear, thanks for the explanation @ChristopherHX!
I'm going to reopen this issue and I'll come back to you when we have more information about the bug itself.
Activity
ruvceskistefan commentedon Mar 31, 2022
Hi @edtan,
I tried to reproduce the reported bug, but I didn't have any success. I'm sending a link to a successfully completed workflow: https://github.com/ruvceskistefan/git-runner-test/runs/5768372718?check_suite_focus=true
Since this does not happen on newer verions of runner, I will close this issue. Feel free to reopen it if the problem still exists or you have more questions.
ChristopherHX commentedon Mar 31, 2022
It does happen, but only in the first step of a job
LOG of runner 2.288.0
ruvceskistefan commentedon Mar 31, 2022
Okay, now it's clear, thanks for the explanation @ChristopherHX!
I'm going to reopen this issue and I'll come back to you when we have more information about the bug itself.
arianvp commentedon Aug 27, 2025
any update on this. this is still broken