test_ok2/changelog
Zac Hatfield-Dodds 3a060b77e8
Revert change to traceback repr (#7535)
* Revert change to traceback repr

* Add test and changelog entry

* Restore *exact* prev output

Co-authored-by: Bruno Oliveira <nicoddemus@gmail.com>
2020-07-24 13:30:38 +02:00
..
5584.breaking.rst Change pytest deprecation warnings into errors for 6.0 release (#7362) 2020-07-22 21:36:51 -03:00
7389.trivial.rst Remove package scope experimental status 2020-06-27 11:16:50 -03:00
7392.bugfix.rst Fix reported location of skip when --runxfail is used (#7432) 2020-07-09 23:10:32 +03:00
7422.doc.rst Clarify usage of usefixtures mark in hooks 2020-07-21 23:00:47 -03:00
7441.doc.rst docs: Add a note about -q option used in getting started guide 2020-07-20 01:28:11 +05:30
7464.feature.rst Use sphinx references for NO_COLOR and FORCE_COLOR in changelog 2020-07-10 09:30:04 -03:00
7467.improvement.rst Create subdirectories if they do not exist when specified for log file (#7468) 2020-07-11 13:40:28 -03:00
7472.breaking.rst Add changelog entry for Frame removals 2020-07-10 13:08:56 +03:00
7489.improvement.rst Clearer guidance on pytest.raise(match=...) failure (#7499) 2020-07-15 22:26:47 +03:00
7491.bugfix.rst Inaccessible lock files now imply temporary directories can't be removed 2020-07-15 09:25:17 -03:00
7517.bugfix.rst Preserve newlines when captured with capfd 2020-07-20 10:31:20 -07:00
7534.bugfix.rst Revert change to traceback repr (#7535) 2020-07-24 13:30:38 +02:00
README.rst docs: use doc/en/_build/html for html output (#6842) 2020-02-29 00:47:30 +01:00
_template.rst Update CHANGELOG template to put issue links at the start of entries 2018-07-07 11:02:33 -03:00

README.rst

This directory contains "newsfragments" which are short files that contain a small **ReST**-formatted
text that will be added to the next ``CHANGELOG``.

The ``CHANGELOG`` will be read by **users**, so this description should be aimed to pytest users
instead of describing internal changes which are only relevant to the developers.

Make sure to use full sentences in the **past or present tense** and use punctuation, examples::

    Improved verbose diff output with sequences.

    Terminal summary statistics now use multiple colors.

Each file should be named like ``<ISSUE>.<TYPE>.rst``, where
``<ISSUE>`` is an issue number, and ``<TYPE>`` is one of:

* ``feature``: new user facing features, like new command-line options and new behavior.
* ``improvement``: improvement of existing functionality, usually without requiring user intervention (for example, new fields being written in ``--junitxml``, improved colors in terminal, etc).
* ``bugfix``: fixes a bug.
* ``doc``: documentation improvement, like rewording an entire session or adding missing docs.
* ``deprecation``: feature deprecation.
* ``breaking``: a change which may break existing suites, such as feature removal or behavior change.
* ``vendor``: changes in packages vendored in pytest.
* ``trivial``: fixing a small typo or internal change that might be noteworthy.

So for example: ``123.feature.rst``, ``456.bugfix.rst``.

If your PR fixes an issue, use that number here. If there is no issue,
then after you submit the PR and get the PR number you can add a
changelog using that instead.

If you are not sure what issue type to use, don't hesitate to ask in your PR.

``towncrier`` preserves multiple paragraphs and formatting (code blocks, lists, and so on), but for entries
other than ``features`` it is usually better to stick to a single paragraph to keep it concise.

You can also run ``tox -e docs`` to build the documentation
with the draft changelog (``doc/en/_build/html/changelog.html``) if you want to get a preview of how your change will look in the final release notes.