Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
S
setuptools
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jérome Perrin
setuptools
Commits
f4eb1393
Commit
f4eb1393
authored
Jan 01, 2019
by
mergify[bot]
Committed by
GitHub
Jan 01, 2019
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #1622 from pganssle/tweak_guide
Tweak "making a pull request" documentation
parents
b82c731a
135a1566
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
docs/developer-guide.txt
docs/developer-guide.txt
+2
-2
No files found.
docs/developer-guide.txt
View file @
f4eb1393
...
@@ -68,7 +68,7 @@ changelog entry.
...
@@ -68,7 +68,7 @@ changelog entry.
``setuptools`` uses `towncrier <https://pypi.org/project/towncrier/>`_
``setuptools`` uses `towncrier <https://pypi.org/project/towncrier/>`_
for changelog management, so when making a PR, please add a news fragment in the
for changelog management, so when making a PR, please add a news fragment in the
``changelog.d/`` folder. Changelog files are written in
Restructured
Text and
``changelog.d/`` folder. Changelog files are written in
reStructured
Text and
should be a 1 or 2 sentence description of the substantive changes in the PR.
should be a 1 or 2 sentence description of the substantive changes in the PR.
They should be named ``<pr_number>.<category>.rst``, where the categories are:
They should be named ``<pr_number>.<category>.rst``, where the categories are:
...
@@ -76,7 +76,7 @@ They should be named ``<pr_number>.<category>.rst``, where the categories are:
...
@@ -76,7 +76,7 @@ They should be named ``<pr_number>.<category>.rst``, where the categories are:
- ``breaking``: Any backwards-compatibility breaking change
- ``breaking``: Any backwards-compatibility breaking change
- ``doc``: A change to the documentation
- ``doc``: A change to the documentation
- ``misc``: Changes internal to the repo like CI, test and build changes
- ``misc``: Changes internal to the repo like CI, test and build changes
- ``deprecation``: For deprecations of an existing feature o
f
behavior
- ``deprecation``: For deprecations of an existing feature o
r
behavior
A pull request may have more than one of these components, for example a code
A pull request may have more than one of these components, for example a code
change may introduce a new feature that deprecates an old feature, in which
change may introduce a new feature that deprecates an old feature, in which
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment