Using concurrency to cancel any in-progress job or run

[blink1073]

Summary of changes

Uses concurrency to cancel any in-progress job or run to help address #3093

Closes

Pull Request Checklist

• Changes have tests (N/A)
• News fragment added in changelog.d/. (N/A)
  (See documentation for details)

[abravalheri]

I don't know exactly but I have the impression that this change accidentally is preventing the release job to run on tags...

For example if we look at the workflow for the tag v60.9.1 (Fig. 1), the message seems to indicate that it got cancelled by GitHub because jobs for the commit being pushed to the main branch got enqueued just after the ones for the tag (Fig. 2):

Fig 1: Workflow for tag is getting cancelled because of a higher priority request

Fig 2: The higher priority request seems to be the normal push to main of the same commit

This might be related to the lack of determinism in the order workflows are triggered...

I don't know exactly how to solve this, but maybe it is a good idea to add the name of the event triggering the workflow to the group string? (if that is even possible)

@blink1073, @di what do you think?

[di]

I think you're right. The 'release' job probably needs to become its own workflow with on: push: tags:

setuptools/.github/workflows/main.yml

Lines 102 to 120 in 5b2b20d

	release:
	needs: [test, test_cygwin, integration-test]
	if: github.event_name == 'push' && contains(github.ref, 'refs/tags/')
	runs-on: ubuntu-latest
	steps:
	- uses: actions/checkout@v2
	- name: Setup Python
	uses: actions/setup-python@v2
	with:
	python-version: "3.10"
	- name: Install tox
	run: |
	python -m pip install tox
	- name: Release
	run: tox -e release
	env:
	TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}