8000 Move NEWS entries to pull-request-lifecycle by StanFromIreland · Pull Request #1506 · python/devguide · GitHub
[go: up one dir, main page]
Skip to content

Move NEWS entries to pull-request-lifecycle #1506

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

Move NEWS entries to pull-request-lifecycle #1506

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
3e489a6
Move _what-s-new-and-news-entries to pull-request-lifecycle
StanFromIreland Feb 3, 2025
6860013
Change to seealso
StanFromIreland Feb 3, 2025
dffca01
Revert seealso
StanFromIreland Feb 3, 2025
fbd50f0
Update core-developers/committing.rst
StanFromIreland Feb 3, 2025
44024a1
seealso works now?
StanFromIreland Feb 3, 2025
431d021
See also works now
StanFromIreland Feb 3, 2025
8000
6f6fbae
Change title levels
StanFromIreland Feb 3, 2025
d145ed5
Apply suggestions from code review
StanFromIreland Mar 13, 2025
11b5c8c
Benedikts suggestions
StanFromIreland Mar 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
seealso works now?
  • Loading branch information
@StanFromIreland
StanFromIreland committed Feb 3, 2025
commit 44024a1dba85e7f9752e1854d84584bf53b9c544
5 changes: 4 additions & 1 deletion core-developers/committing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,10 @@ to enter the public source tree. Ask yourself the following questions:
significant improvements, or backwards-incompatible changes), then an
entry in the ``What's New in Python`` document (in ``Doc/whatsnew/``) should
be added as well. Changes that affect only documentation generally do not
require a ``NEWS`` entry. (See :ref:`what-s-new-and-news-entries`)
require a ``NEWS`` entry.

.. seealso::
:ref:`what-s-new-and-news-entries`


Working with Git_
Expand Down
0