| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Updated the "making a good PR" section of the page with tips on creating the title and description
Sorry, something went wrong.
| issue resolution. It is the initial point of contact in a code review, and | ||
| allows the code reviewer to quickly assess the issue. The suggested formatting | ||
| of the title and description is | ||
| **[type(optional) title: description (issue number)]** where type is the label |
There was a problem hiding this comment.
I don't understand this, where is the gh-XXXXX, and what is type?
An example title:
GH-132732: Use pure op machinery to optimize various instructions with _POP_TOP and _POP_TWO
Sorry, something went wrong.
Updated the title formatting, and provided an example. Also removed trailing whitespaces.
pythonGH-931: Update pull-request-lifecycle.rst PR title and description section
| Here is an example of a poor and revised pull request description: | ||
| **Poor Pull Request:** "update code" **Revised Pull Request:** | ||
| "feat: add search functionality to user dashboard(closes #111)" |
There was a problem hiding this comment.
This has the same issue I mentioned above (which was correct).
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Updated the "making a good PR" section of the page with tips on creating the title and description
#931📚 Documentation preview 📚: https://cpython-devguide--1626.org.readthedocs.build/