test_ok2/changelog
Milan Lesnek 6badb6f01e Apply suggestions from code review
chore(changelog): describe better the fix

Co-authored-by: Zac Hatfield-Dodds <zac.hatfield.dodds@gmail.com>
2023-07-04 10:30:19 +02:00
..
3664.deprecation.rst Update changelog/3664.deprecation.rst 2022-10-10 12:28:14 +01:00
7363.breaking.rst Change PytestRemovedIn8Warning to error by default 2023-06-23 16:42:24 +03:00
8976.breaking.rst python: change `pytest pkg/__init__.py` to only collect the `__init__.py` Module 2023-06-23 20:42:50 +03:00
9036.bugfix.rst capture warning when exception is raised (fix #9036) 2023-06-30 16:04:37 -07:00
9288.breaking.rst Tweak docs on review 2023-06-30 15:29:03 -07:00
10337.bugfix.rst Added Akhilesh Ramakrishnan to AUTHORS (#11153) 2023-07-03 13:49:50 +02:00
10447.bugfix.rst fix #10447 - consider marks in reverse mro order to give base classes priority 2023-07-01 22:27:18 +02:00
10701.bugfix.rst Apply suggestions from code review 2023-07-04 10:30:19 +02:00
10811.bugfix.rst Fix duplicated imports with importlib mode and doctest-modules (#11148) 2023-07-01 15:37:46 +00:00
11011.doc.rst add a warning about modifying the root logger during tests 2023-05-18 09:26:16 -05:00
11151.breaking.rst Apply suggestions from code review 2023-06-30 20:18:25 -07: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.