Replies: 3 comments
-
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 |
Beta Was this translation helpful? Give feedback.
-
I'm experiencing the same issue. One odd detail is that using Works As ExpectedCaller: ---
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 (
|
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
I have a callable workflow, where I use this to avoid concurrency
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 likegithub.event.number
is empty. It seems the wholegithub.event
does not exist here, as e.g.github.event.action
is also an empty string. All I can see thatgithub.event_name
ispull_request
.When I add jobs in this workflow, then
github.event
works there as expected.Beta Was this translation helpful? Give feedback.
All reactions