Why are Travis/Appveyor always uploading wheels?

[banesullivan]

The Travis and Appveyor scripts upload a built wheel on every build...

GSTools/.travis.yml

Lines 123 to 127 in 5326163

	after_success:
	# pypi upload ("test" allways and "official" on TAG)
	- python -m pip install twine
	- python -m twine upload --verbose --skip-existing --repository-url https://test.pypi.org/legacy/ wheelhouse/*.whl
	- python -m twine upload --verbose --skip-existing --repository-url https://test.pypi.org/legacy/ dist/*.tar.gz

GSTools/appveyor.yml

Line 12 in 5326163

- python -m twine upload --skip-existing --repository-url https://test.pypi.org/legacy/ wheelhouse/*.whl

Why? This seems excessive and it will cause a failed build on PRs from any forks (see #57 and #59)

[MuellerSeb]

You need to make the PRs in the develop branch, since the master branch only holds the latest release.

The .travis.yaml was updated in this branch:

GSTools/.travis.yml

Line 104 in 4bde6a0

if [[ $TRAVIS_PULL_REQUEST == 'false' ]]; then

So the exact thing you described was already solved. ;-)

[LSchueler]

I just clarified from which branch to fork in the CONTRIBUTING.MD

[MuellerSeb]

@LSchueler : thx! 👍