Documentation: Compare with native `concurrency` key about cancel-workflow-action HOT 5 CLOSED

Trying to implement the concurrency at the job level in a multi-job workflow and getting a properties error.

.github/workflows/deploy-gluon-api.yml failed test
[
  {
    instancePath: '/jobs/deploy-dev-canary',
    schemaPath: '#/properties/jobs/patternProperties/%5E%5B_a-zA-Z%5D%5Ba-zA-Z0-9_-%5D*%24/additionalProperties',
    keyword: 'additionalProperties',
    params: { additionalProperty: 'concurrency' },
    message: 'must NOT have additional properties'
  }
]

implementation in workflow for context:

jobs:
  job1:
  ...

  deploy-dev-canary:
    concurrency:
      group: ${{ github.ref }}
      cancel-in-progress: true
    environment:
      name: "appname-dev-canary"
    needs: setup
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      ...

What is wrong with my implementation at the job level?

from cancel-workflow-action.

That looks really cool - appears to be nice for cases where you want to cancel previous of same workflow - plus obviously for things where you are interested in making sure multiple jobs don't run in parallel

But it does not handle other-workflow cancel or the new (super useful) all_but_latest feature here

from cancel-workflow-action.

Very cool! Looks like its still in beta and subject to change though.

https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#concurrency

from cancel-workflow-action.

Yep, it also seems to not work as expected right now:

• https://github.community/t/concurrency-cancel-in-progress-at-top-level-doesnt-seem-to-cancel-running-workflows/175801/6
• https://github.community/t/actions-concurrency-bug-report/175695

from cancel-workflow-action.

Also mentioned here #133 (comment)

from cancel-workflow-action.