Workflows with identical concurrency groups at workflow and job level appear valid but will never run

[thyeggman]

Describe the bug If a concurrency group is defined at the workflow level, and the same concurrency group is defined at the job level, the job will never run. It will be skipped with the following error:

Canceling since a deadlock for concurrency group '<group name>' was detected between 'top level workflow' and '<job name>'

These workflows do not produce any warnings in the editor, even though they will never run. Here is a link to a workflow run that is skipped in this way.

To Reproduce Steps to reproduce the behavior:

1. Create this workflow:

on:
  workflow_dispatch:
concurrency: test

jobs:
  deadlock:
    runs-on: ubuntu-latest
    concurrency: test
    steps:
      - name: echo something
        run: echo "Hi"

2. Observe that there are no warnings or errors in the editor

Expected behavior One or both concurrency groups should have a warning (yellow underline) with a note mentioning that there will be a conflict between identical concurrency groups in the same workflow.

Screenshots Workflow showing no errors:

Extension Version v0.25.5