parent
dbb58b39d9
commit
019dc14fc4
|
@ -3,7 +3,7 @@
|
||||||
|
|
||||||
- add ability to set command line options by environment variable PYTEST_ADDOPTS.
|
- add ability to set command line options by environment variable PYTEST_ADDOPTS.
|
||||||
|
|
||||||
- added documentationo on the new pytest-dev teams on bitbucket and
|
- added documentation on the new pytest-dev teams on bitbucket and
|
||||||
github. See https://pytest.org/latest/contributing.html .
|
github. See https://pytest.org/latest/contributing.html .
|
||||||
Thanks to Anatoly for pushing and initial work on this.
|
Thanks to Anatoly for pushing and initial work on this.
|
||||||
|
|
||||||
|
|
|
@ -209,10 +209,10 @@ Mercurial one, to remove confusion of people not knowing where it's better to
|
||||||
put their issues and pull requests. Also it wasn't easily possible to automate
|
put their issues and pull requests. Also it wasn't easily possible to automate
|
||||||
the mirroring process.
|
the mirroring process.
|
||||||
|
|
||||||
However, it's still possible to use git to contribute to pytest using tools
|
In general we recommend to work with the same version control system of the
|
||||||
like `gitifyhg <https://github.com/buchuki/gitifyhg>`_ which allows you to
|
original repository. If you insist on using git with bitbucket/hg you
|
||||||
clone and work with Mercurial repo still using git.
|
may try `gitifyhg <https://github.com/buchuki/gitifyhg>`_ but are on your
|
||||||
|
own and need to submit pull requests through the respective platform,
|
||||||
|
nevertheless.
|
||||||
|
|
||||||
|
|
||||||
.. warning::
|
|
||||||
Remember that git is **not** a default version control system for pytest and
|
|
||||||
you need to be careful using it.
|
|
||||||
|
|
Loading…
Reference in New Issue