github.event does not exist in called workflow for concurrency group naming?

[axel-h]

Select Topic Area

Bug

Body

I have a callable workflow, where I use this to avoid concurrency

name: myCallableWorkflow

on:
  workflow_call:    # to be called for pushes in pull requests

concurrency:
  group: ${{ github.workflow }}-myCallableWorkflow-pr-${{ github.event.number }}

I can see that a newer run kills the older one. But the concurrency group name is shown as callerWorkflowName-myCallableWorkflow-pr-, so it looks like github.event.number is empty. It seems the whole github.event does not exist here, as e.g. github.event.action is also an empty string. All I can see that github.event_name is pull_request.
When I add jobs in this workflow, then github.event works there as expected.

[axel-h]

Is this similar to what https://github.com/orgs/community/discussions/13496 ran into? So the value of concurrency group is evaluated on the GitHub Actions server, not on the runner. However, the github.event context is set by the runner?

[nwiltsie]

I'm experiencing the same issue. One odd detail is that using github.event in a workflow-level concurrency block does work in the calling workflow.

Works As Expected

Caller:

---
name: Trigger tests
on:
  issue_comment:
    types: [created]

concurrency:
  cancel-in-progress: true
  group: ${{ github.repository }}-${{ github.event.issue.number }}

jobs:
  check-user:
    uses: ... (workflow in another repository)

Callee:

name: Test Setup

on:
  workflow_call:

jobs:
  configure:
    runs-on: ubuntu-latest
    ...

Does Not Work (github.event.issue.number is blank)

Caller:

---
name: Trigger tests
on:
  issue_comment:
    types: [created]

jobs:
  check-user:
    uses: ... (workflow in another repository)

Callee:

name: Test Setup

on:
  workflow_call:

concurrency:
  cancel-in-progress: true
  group: ${{ github.repository }}-${{ github.event.issue.number }}

jobs:
  configure:
    runs-on: ubuntu-latest
    ...

[axel-h]

Yes, I have also noticed this, as my called workflow was basically a clone of the original workflow, which got tuned into a wrapper then.

[gtjoseph]

I just ran into this as well. I'm fairly certain ${{ github.event.number }} works at the workflow level in a calling workflow but it's blank if you move the concurrency into a job in the same file that calls a reusable workflow. It seems like every week I run into yet another github actions limitation.