]> git.madduck.net Git - etc/vim.git/commitdiff

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

Rename design label to style because it's clearer (#3547)
authorRichard Si <sichard26@gmail.com>
Sun, 5 Feb 2023 03:51:46 +0000 (22:51 -0500)
committerGitHub <noreply@github.com>
Sun, 5 Feb 2023 03:51:46 +0000 (22:51 -0500)
.github/ISSUE_TEMPLATE/style_issue.md
docs/contributing/issue_triage.md
docs/the_black_code_style/index.md

index 2e4343a3527be07f0c1f5500f63c9c7ed1b96a33..a9ce85fd977a1144f84da86540e7ae9708f9c22f 100644 (file)
@@ -1,8 +1,8 @@
 ---
 ---
-name: Style issue
-about: Help us improve the Black style
+name: Code style issue
+about: Help us improve the Black code style
 title: ""
 title: ""
-labels: "T: design"
+labels: "T: style"
 assignees: ""
 ---
 
 assignees: ""
 ---
 
index 865a47935ed7fe0d97ed3a23bcb8f5aa3f8e90cc..aa3e49a649b1e7d24e7ac477e8f47c6966a9e16a 100644 (file)
@@ -1,6 +1,6 @@
 # Issue triage
 
 # Issue triage
 
-Currently, _Black_ uses the issue tracker for bugs, feature requests, proposed design
+Currently, _Black_ uses the issue tracker for bugs, feature requests, proposed style
 modifications, and general user support. Each of these issues have to be triaged so they
 can be eventually be resolved somehow. This document outlines the triaging process and
 also the current guidelines and recommendations.
 modifications, and general user support. Each of these issues have to be triaged so they
 can be eventually be resolved somehow. This document outlines the triaging process and
 also the current guidelines and recommendations.
@@ -53,7 +53,7 @@ The lifecycle of a bug report or user support issue typically goes something lik
    - the issue has been fixed
    - duplicate of another pre-existing issue or is invalid
 
    - the issue has been fixed
    - duplicate of another pre-existing issue or is invalid
 
-For enhancement, documentation, and design issues, the lifecycle looks very similar but
+For enhancement, documentation, and style issues, the lifecycle looks very similar but
 the details are different:
 
 1. _the issue is waiting for triage_
 the details are different:
 
 1. _the issue is waiting for triage_
index e5967be2db4f9cacf01a363d43dd6f471d6051b3..1719347eec81ae97a10f181e149a6fb2194acbcc 100644 (file)
@@ -17,7 +17,7 @@ Python language and, occasionally, in response to user feedback. Large-scale sty
 preferences presented in {doc}`current_style` are very unlikely to change, but minor
 style aspects and details might change according to the stability policy presented
 below. Ongoing style considerations are tracked on GitHub with the
 preferences presented in {doc}`current_style` are very unlikely to change, but minor
 style aspects and details might change according to the stability policy presented
 below. Ongoing style considerations are tracked on GitHub with the
-[design](https://github.com/psf/black/labels/T%3A%20design) issue label.
+[style](https://github.com/psf/black/labels/T%3A%20style) issue label.
 
 (labels/stability-policy)=
 
 
 (labels/stability-policy)=