be0c41bf8e
CI: Test latest 3.10 available
2022-02-11 13:49:11 +02:00
dff1a15881
ci: Add missing macOS CI envs ( #9601 )
...
alinsa_vix in Discord noticed that we are not testing Python 3.9 and 3.10 on macOS, which seems strange. Maybe this is due how to macOS CI resources were quite scarce for a while, but I believe this has improved since.
2022-02-04 12:11:30 +01:00
6e1445b521
ci: Bump up timeout ( #9560 )
...
macOS apparently can be slow, https://github.com/pytest-dev/pytest/runs/4965510831 for #9556 got cancelled at 91%
2022-01-27 13:33:20 +01:00
d60771f986
ci: Try backporting via pull_request_target ( #9430 )
...
* ci: Try backporting via pull_request_target
* ci: Security improvements
2022-01-03 14:14:40 +00:00
819c67f58e
Also test branches prefixed test-me-
2022-01-01 23:36:10 +02:00
b9663fed6f
Merge pull request #9442 from hramezani/drop_python_36
...
Drop Python3.6 in CI, setup.cfg, and readme.
2021-12-30 12:22:13 +02:00
1522afa1cd
ci: run plugins job with python 3.9 instead of 3.7
...
Latest Django release dropped support for 3.7.
2021-12-28 11:01:23 +02:00
5599c5ad45
Drop Python3.6 in CI, setup.cfg, and readme.
2021-12-26 21:08:37 +01:00
913439f5e5
Fix test_errors_in_xfail_skip_expressions for Python 3.10.1
...
Decided to remove the condition altogether as seems reasonable to state
that our own test suite requires Python 3.10.1.
Fix #9413
2021-12-16 10:18:07 -03:00
c85b14391d
ci: add a workflow for backporting to other branches
...
To backport a PR, e.g. 1000, to another branch, e.g. `7.0.x`, add a
label `backport 7.0.x` to the PR. This will trigger a workflow which
will create a branch `backport-1000-to-7.0.x` based on the `7.0.x`
branch with a cherry-pick of the PR's merge commit, and create a new PR
for it against the `7.0.x` branch.
It is very simplistic, for instance it doesn't handle cherry-pick
failure gracefully, doesn't validate the state of the PR, doesn't check
if the branch already exists, etc. But we can improve on it later as
needed.
Finally, PRs created by github actions do not themselves trigger further
actions, i.e. the PR isn't checked. You need to close & reopen the PR
for the checks to trigger. There are workarounds for this but they are
either less secure or require more setup.
2021-12-12 01:12:35 +02:00
f288afde1d
Use codecov github action instead of deprecated bash uploader ( #9252 )
...
Fixes #9202 .
2021-11-01 17:41:56 +02:00
69b0a7b306
ci: remove linting job - covered be pre-commit.ci ( #9247 )
2021-10-29 19:23:47 -03:00
bcad6e8e9a
Make plugin list in PDF docs readable ( #9241 )
...
The current PDF docs attempt to format the list of all plugins as a
table, without any word-wrapping of the plugin description. That results
in almost all the information getting cut off. This PR formats the same
information into more of a paragraph format for the PDF, with nothing
cut off.
Fixes #451
2021-10-28 11:31:52 +03:00
14e032088c
Change the command for package building in release CI workflow ( #9229 )
2021-10-25 21:32:12 +03:00
0892c77bc6
fixes #8133 : mitigate regendoc issues wrt PRETEND_VERSION
...
this issues is less likely to hit due to the recent regendoc release
which includes a wheel
* migrate to setuptools_scm 6.3.2
* use SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST
2021-10-02 20:22:18 +02:00
675f8da3a1
Fix prepare-release-pr invocation with empty --prerelease argument
2021-08-27 14:46:28 -03:00
9501e54852
'prerelease' input is not required in prepare-release-pr workflow
...
The default is the correct value when generating a normal release.
2021-08-27 14:26:30 -03:00
4d965557e2
ci: Persist git credentials for prepare-release-pr ( #8813 )
...
See #8599 , follow-up to #8681
2021-06-28 20:58:55 +02:00
c19f63d39d
Adjust releasing infra/docs ( #8795 )
...
* Adjust releasing infra/docs
Follow-up for #8150 , see #7507
* Add suggestions
2021-06-28 12:24:48 +02:00
0d6cb3b281
Allow prereleases from prepare-release workflow ( #8628 )
...
Fix #7551
2021-06-24 18:05:56 +00:00
864a2bc0a3
ci: use GitHub Actions token instead of `chatops`/`release_notes` secrets
...
It seems more secure to use the controlled & limited token than an
ambient secret.
2021-05-18 16:05:14 +03:00
6bc6ec323a
ci: reduce workflow permissions
...
Decrease security exposure by restricting what the code executing in the
actions is allowed to do (in terms of GitHub operations).
2021-05-18 16:05:14 +03:00
3f71d63067
ci: Force colors on
...
See #7443
2021-05-04 17:55:47 +02:00
8c65a4f174
Configure support for Python 3.10
2021-03-26 07:33:24 -03:00
a6cf0a0a0e
rename master to main in PULL_REQUEST_TEMPLATE.md ( #8481 )
2021-03-22 22:06:46 +00:00
dbed1ff68f
adopt main terminology in the configs
...
ref pytest-dev/meta#8
2021-03-09 22:35:34 +01:00
e3c0fd3203
Update plugin-list every Sunday instead of everyday
...
Every day seems a bit excessive lately, let's make it less frequent.
2021-02-05 07:29:12 -03:00
c971f2f474
ci: give pytest bot the credit for updating the plugin list
2021-01-30 13:04:10 +02:00
beda7a8a31
Add plugin list
2021-01-29 16:19:54 +02:00
8550c29180
coverage: Include code that runs in subprocesses
2020-12-26 16:59:07 -08:00
293a7c962d
Use new pypy3 github actions syntax
2020-12-18 10:45:28 -08:00
4da445dc2e
Revert "infra: Temporary pin setup-python GH action to v2.1.4"
2020-12-18 10:44:20 -08:00
1264404fe7
infra: Temporary pin setup-python GH action to v2.1.4
2020-12-17 21:01:20 -08:00
a1c5111a40
Fix events variable in prepare-release-pr.yml
2020-12-16 07:53:05 -03:00
f1a1de2257
Use manual trigger to prepare release PRs ( #8150 )
...
Co-authored-by: Ran Benita <ran@unusedvar.com>
2020-12-16 07:50:02 -03:00
cf1051cfba
infrastructure: Stricter tox dependensies ( #8119 )
2020-12-12 18:08:15 +02:00
537215a16c
Merge pull request #7987 from bluetech/ci-deprecated
...
ci: fix deprecation message & couple updates
2020-11-16 23:29:35 +02:00
701ff1f5a1
ci: only deploy to PyPI on X.Y.Z{,rcN} tags
...
We want to reserve other tags for our own purposes without it creating a
release.
2020-11-13 12:38:30 +02:00
8aa9ea95e1
ci: test on Python 3.9 final
2020-11-01 09:49:41 +02:00
76226182ae
ci: change cache action to v2
...
Supposed to be faster.
2020-11-01 09:49:41 +02:00
f9d82a34f4
ci: replace deprecated ::set-env
2020-11-01 09:49:23 +02:00
e14b724ff4
Update .github/ISSUE_TEMPLATE/2_feature_request.md
2020-10-23 22:35:56 +01:00
03363473f7
expand feature request issue template
2020-10-23 14:03:24 +01:00
fe69d0d680
ci: decrease job timeout from 6 hours to 30 minutes
...
We don't have any jobs that should go beyond that, so let's be nicer to
the CI host and quicker to report the failure.
2020-10-21 10:17:25 +03:00
3059caf1ee
Put smoke test deps in requirements.txt for Dependabot ( #7806 )
2020-10-10 18:51:35 +03:00
179f4326df
py36+: drop python3.5 in CI and setup.cfg
2020-10-02 14:00:11 -07:00
32bb8f3a63
Bump attrs requirement from >=17.4.0 to >=19.2.0
...
This allows us to remove the `ATTRS_EQ_FIELD` thing which is causing
some annoyance.
2020-09-27 13:17:59 +03:00
050c2df737
Use multiple issue template types and mention Discussions ( #7739 )
2020-09-21 20:22:25 +02:00
b031a7cecf
Smoke tests for assorted plugins ( #7721 )
...
Co-authored-by: Bruno Oliveira <nicoddemus@gmail.com>
Co-authored-by: Thomas Grainger <tagrain@gmail.com>
Co-authored-by: Kyle Altendorf <sda@fstab.net>
2020-09-19 15:56:52 -03:00
a5fd2895b6
Update to deadsnakes/action@v2.0.0
...
should be a noop (despite the major version bump) -- I rewrote the action to be more stable and need fewer security updates
2020-09-13 12:55:56 -07:00
c871d8b2b6
Merge pull request #7304 from asottile/cache_pre_commit
...
cache the pre-commit environment
2020-06-09 10:56:42 -03:00
96d4e2f571
Add documentation on closing issues
2020-06-08 23:58:44 -04:00
8cca023840
cache the pre-commit environment
2020-06-02 12:30:10 -07:00
9214e63af3
ci: use fetch-depth: 0 instead of fetching manually ( #7297 )
2020-06-02 10:29:36 +03:00
c9abdaf381
Use deadsnakes/action@v1.0.0 to install python3.9 nightly
2020-05-23 19:51:51 -07:00
c66bf59fd5
ci: update github action versions, remove outdated comment ( #7177 )
2020-05-08 13:03:51 +03:00
dad328bc8a
Fix tests for python3.9
2020-05-07 05:26:55 -07:00
fd2f172258
Let unittest frameworks deal with async functions
...
Instead of trying to handle unittest-async functions in pytest_pyfunc_call,
let the unittest framework handle them instead.
This lets us remove the hack in pytest_pyfunc_call, with the upside that
we should support any unittest-async based framework.
Also included 'asynctest' as test dependency for py37-twisted, and renamed
'twisted' to 'unittestextras' to better reflect that we install 'twisted' and
'asynctest' now.
This also fixes the problem of cleanUp functions not being properly called
for async functions.
Fix #7110
Fix #6924
2020-05-01 15:10:28 -03:00
2cc3227f6a
ci: twisted and oldattrs tox envs are now incompatible, don't run them together
...
twisted started to use `attr.s(eq)` argument which was added recently,
so it fails with oldattrs. One of the CI jobs ran twisted and oldattrs
together, so it started to fail.
Move the twisted code to be covered by another job, and remove it from
the job with the oldattrs.
2020-03-21 16:22:33 +02:00
a0ea300e96
Fix bot trigger event
...
Issue events don't contain a 'comment' entry:
https://developer.github.com/v3/issues/events/#response-2
Issue comments also contain the original issue body:
https://developer.github.com/v3/activity/events/types/#issuecommentevent
That's why it was triggering even for comments on the issue.
Also changed to startsWith because there's no need to support
the command anywhere in the body IMO.
Fix #6895
2020-03-11 09:54:56 -03:00
15e1dd0f87
Automate release by comment notifications ( #6823 )
...
* Automate release by comment notifications
* Only run if @pytestbot is mentioned
2020-03-01 14:46:35 -03:00
c3e53a072d
Switch to new git workflow
...
Co-Authored-By: Daniel Hahler <git@thequod.de>
2020-02-12 09:49:21 +02:00
1480aa31a7
Explicitly state on the PR template that we can squash commits ( #6662 )
...
* Explicitly state on the PR template that we can squash commits
This way we don't need to ask every time, and users who for some reason
would not like us to squash their commits can explicitly state so.
2020-02-03 14:35:50 -03:00
b2e6f66438
ci: GHA: run less jobs with coverage
...
This often might be causing for jobs to take longer than 10 minutes,
which is a timeout Codecov uses to wait for successful CI.
Also it is good in general to have CI finish faster, of course.
2020-01-28 17:38:53 +01:00
934f38995a
ci: GHA: codecov: set CODECOV_NAME, OS in flags
2020-01-24 19:42:51 +01:00
e5a362d0f5
ci: GHA: use scripts/report-coverage.sh
2020-01-24 18:00:38 +01:00
c051a9e7b9
ci: GHA: separate jobs for linting, docs, doctesting
...
It helps to know upfront that e.g. linting failed, and makes finding the
error easier.
2020-01-24 12:29:35 +01:00
a8d67f5e7b
ci: codecov: add flags for GHA/Travis
...
This would help with debugging missing coverage when removing Travis
jobs.
2020-01-23 15:41:41 +01:00
9869a3d9e1
ci: GHA: remove unnecessary check for `success()`
...
Following jobs get aborted on failure.
Ref: https://github.com/pytest-dev/pytest/pull/6530
2020-01-21 21:44:49 +01:00
ea31649062
ci: github actions: only deploy pytest-dev/pytest
2020-01-16 13:57:46 +01:00
1d3f27cef0
Add deploy step: publish package and release notes
...
Fix #6369
2020-01-15 08:11:35 -03:00
d291905825
Append token to codecov.yml instead of duplicating the file
2020-01-14 07:47:21 -03:00
a3bc6df950
Implement code coverage in GitHub actions
...
This overwrites the `codecov.yml` file in the root of the repository with
`codecov-upstream.yml` file (which contains the code-cov token)´, so PRs
and branches on the repository can upload coverage.
Suggestion from here:
https://github.com/pytest-dev/pytest/pull/6421#issuecomment-571934112
Security concerns: the token might be misused, but only to upload bogus coverage
to `codecov.io`, so the team believe this is harmless. If we decide to fallback
from this decision , we just need to revoke the token.
Related to #6369
2020-01-11 12:21:20 -03:00
d76aa8b428
Add GitHub actions for CI
...
This includes our current full matrix (windows, linux and macos), for evaluting
purposes.
We should disconsider failures when evaluating PRs.
TODO:
- deploy
- coverage
- github release notes
Even with the above missing, I still believe it would be nice to merge
this and have GitHub actions working in parallel so we can evaluate performance
and usability from now on.
2019-12-19 11:06:57 -03:00
36ef545b2d
Improve instructions on how to write CHANGELOG entries
...
This makes easier for contributors to get the CHANGELOG entry
right the first time.
2019-11-19 14:15:55 -03:00
48ec7d28c6
Make whole checklist a comment to avoid incomplete TODOs in PRs
2019-11-14 12:01:40 +02:00
350c27c8b4
Update text in PR template
2019-11-14 11:36:47 +02:00
beb457c75e
Add new 'improvement' changelog category
...
This creates a separate section from 'features' for small changes which
don't usually require user intervention, such as:
* Human readable session duration
* New junitxml fields
* Improved colors in terminal
* etc.
The idea is to better match user expectations about new actual
features in the "Features" section of the changelog.
2019-08-10 09:33:51 -03:00
2479a91e92
Add Open Collective to FUNDING.yml
2019-06-27 17:53:03 +02:00
e393a73890
Small change to test if pushing directly to master is disabled
2019-05-24 12:11:15 -03:00
aaea4e52ef
Fix whitespace in FUNDING.yml
2019-05-23 12:44:55 -03:00
0cacdadc97
Create FUNDING.yml
...
Following instructions from:
* https://tidelift.com/subscription/how-to-connect-tidelift-with-github
* https://help.github.com/en/articles/displaying-a-sponsor-button-in-your-repository#displaying-a-sponsor-button-in-your-repository
2019-05-23 12:36:46 -03:00
0571e1ee8e
Make it clear that small typos in docs don't require a CHANGELOG entry
...
From: https://github.com/pytest-dev/pytest/pull/5273#issuecomment-493076587
2019-05-16 10:54:50 -03:00
3df32e2732
GitHub: revisit issue/PR templates [ci skip]
...
The motivation here is to not have the same boilerplate with PRs.
2019-04-23 18:01:13 +02:00
f2174c16cc
Add rtd-bot configuration file [skip appveyor] [skip travis]
...
Part of the configuration necessary for https://github.com/apps/rtd-helper
2019-01-13 20:38:19 -02:00
9e867ce864
Use full link to changelog's README in PR template
...
Fix #4156
2018-10-15 12:19:52 -03:00
35ffd29404
Manage GH labels using the new 'labels' tool
2018-07-14 10:12:52 -03:00
eea169e515
Code review suggestions
2018-02-08 08:03:14 -02:00
40d0ade2d9
Add changelog/README.rst and streamline our PR template text
...
This streamlines the PR template text and adds a more in-depth explanation
about how the changelog entries work because this topic is a common source of
confusion:
- How to name the files.
- Which formatting to use (people in general assume it is Markdown).
- Recommend adding `.rst` extension to changelog files to help with the
above (`towncrier` doesn't care).
This was heavily inspired by the excellent python-trio/trio docs.
2018-02-06 22:20:39 -02:00
cbdab02d05
Fix example in PR template
2017-12-05 20:05:35 +01:00
fe560b7192
Make CONTRIBUTING and PR template more consistent regarding doc contributions
2017-10-23 18:46:14 -02:00
b74c626026
switch changelog management to towncrier
2017-05-30 15:54:15 +02:00
10433db225
Mention small doc fixes don't need tests/changelog entries in PR template
2016-10-05 15:36:38 -03:00
c2864aba3d
Merge branch 'master' into merge-master
...
# Conflicts:
# AUTHORS
# CHANGELOG.rst
# _pytest/monkeypatch.py
# _pytest/python.py
2016-07-25 19:06:29 -03:00
018acc6bae
Explain why thanks yourself in the CHANGELOG
2016-07-23 10:44:38 -03:00
ef9dd14963
Introduce pytest command as recommended entry point
...
Fixes #1629
2016-06-21 16:16:57 +02:00
b46c7dddaa
Fix 'check' in markdown for github templates
2016-03-11 18:22:15 -03:00
b76de91474
Add issue and PR GitHub templates
2016-02-18 18:26:38 -02:00
Hugo van Kemenade
Florian Bruhin
Ran Benita
Hasan Ramezani
Bruno Oliveira
Cristian Vera
andrewdotn
Alexander King
Ronny Pfannschmidt
Simon K
Maximilian Cosmo Sitter
antonblr
Anthony Sottile
Anton
Thomas Grainger
Sorin Sbarnea
Gleb Nikonorov
Bruno Oliveira
Daniel Hahler
Florian Bruhin
Ronny Pfannschmidt
Dave Hunt