Now `tox -e docs` will also include the draft changelog for the
next version (locally only).
`CHANGELOG.rst` now only points to the changelog on READTHEDOCS so
sphinx diretives can be used.
Followup to https://github.com/pytest-dev/pytest/pull/6272
Recently sometimes Azure has failed with:
++ curl -s https://codecov.io/bash
bash: /dev/fd/63: No such file or directory
This attempts to fix this by modifying report-coverage.sh slightly.
I was doing final tests on the script today, and forgot to change
the hardecoded "pytest-dev/pytest", which ended up publishing a
`4.99.10` release to the main repository by mistake, as my token
has access to both my fork and main repository.
I deleted the tag immeditely just a few seconds later, so hopefully
this won't cause major problems.
This change makes it safer to test this in the future, never publishing
to the main repository by mistake (as long as the tags are pushed to the
right repositories of course).
This should increase coverage for subprocesses, where previously
`source` paths were used only from the config file, but not the initial
`--source` argument.
Following the lead from tox, use a simple Python script instead of depending
on ``invoke``.
Other changes:
* Some colors using ``colorama``.
* Run ``pre-commit`` before the final commit to ensure everything is neatly
formatted.
* Drop generating local tag: legacy from the time we used ``devpi`` as staging
area, currently we no longer use it, and we should push a
tag from the last HEAD of the PR always to ensure it is correct.
Because setuptools_scm already includes all version-controlled files
in an sdist, we don't need to maintain a MANIFEST.in file and anymore
See pytest-dev/pytest-xdist#161
Daniel Hahler
Bruno Oliveira
Bruno Oliveira
Steffen Schroeder
Ran Benita
Anthony Sottile
Steve Piercy
Ronny Pfannschmidt
Ronny Pfannschmidt