Concurrency-job-level #4
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

This pull request introduces job-level concurrency control to the workflow queue action, allowing users to prevent specific jobs from running concurrently across workflow runs, in addition to the existing workflow-level concurrency. The changes include updates to usage documentation, input parameters, and core logic to support this feature.
Job-level concurrency support:
job-nameinput inaction.yml, enabling users to specify a job for concurrency control instead of the whole workflow.src/index.jsandsrc/lib/index.jsto handle the newjob-nameinput, passing it through to the concurrency check and updating log messages for clarity. [1] [2] [3] [4]src/lib/runs.jsto check for active runs of the specified job by querying jobs within each workflow run, and returning only those runs where the target job is currently running.Documentation updates:
README.mdto document job-level concurrency, including usage examples, behavior, and a description of the new input parameter. [1] [2]