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
Bruno Oliveira
Florian Bruhin
Bruno Oliveira
Daniel Hahler
Florian Bruhin
Ronny Pfannschmidt
Dave Hunt