tests

Fix layer creation bug #35

	# This workflows will upload a Python Package using Twine when a release is created
	# For more information see: https://help.github.com/en/actions/language-and-framework-guides/using-python-with-github-actions#publishing-to-package-registries

	name: tests

	on:
	push:
	branches:
	- main
	- npe2
	tags:
	- "v" # Push events to matching v, i.e. v1.0, v20.15.10
	pull_request:
	branches:
	- main
	- npe2
	workflow_dispatch:

	jobs:
	build_sdist:
	# this will run when you have tagged a commit, starting with "v*"
	# and requires that you have put your twine API key in your
	# github secrets (see readme for details)
	name: Build source distribution
	if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v')
	runs-on: ubuntu-latest
	steps:
	- uses: actions/checkout@v3

	- name: Build sdist
	run: pipx run build --sdist

	- uses: actions/upload-artifact@v3
	with:
	path: dist/*.tar.gz
	upload_pypi:
	needs: [build_sdist]
	if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v')
	runs-on: ubuntu-latest
	# upload to PyPI on every tag starting with 'v'
	# alternatively, to publish when a GitHub Release is created, use the following rule:
	# if: github.event_name == 'release' && github.event.action == 'published'
	steps:
	- uses: actions/download-artifact@v3
	with:
	# unpacks default artifact into dist/
	# if `name: artifact` is omitted, the action will create extra parent dir
	name: artifact
	path: dist

	- uses: pypa/[email protected]
	with:
	password: ${{ secrets.TWINE_API_KEY }}
	# To test: repository_url: https://test.pypi.org/legacy/

Provide feedback