]> git.madduck.net Git - etc/vim.git/blobdiff - .github/ISSUE_TEMPLATE/style_issue.md

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:

Fix most blib2to3 lint (#3794)
[etc/vim.git] / .github / ISSUE_TEMPLATE / style_issue.md
index 4810ea415fedf8629665deba0fba79e7f38bf21c..a9ce85fd977a1144f84da86540e7ae9708f9c22f 100644 (file)
@@ -1,29 +1,37 @@
 ---
-name: Style issue
-about: Help us improve the Black style
+name: Code style issue
+about: Help us improve the Black code style
 title: ""
-labels: design
+labels: "T: style"
 assignees: ""
 ---
 
-**Describe the style change** A clear and concise description of how the style can be
-improved.
+**Describe the style change**
 
-**Examples in the current _Black_ style** Think of some short code snippets that show
-how the current _Black_ style is not great:
+<!-- A clear and concise description of how the style can be
+improved. -->
 
-```
+**Examples in the current _Black_ style**
+
+<!-- Think of some short code snippets that show
+how the current _Black_ style is not great: -->
+
+```python
 def f():
     "Make sure this code is blackened"""
     pass
 ```
 
-**Desired style** How do you think _Black_ should format the above snippets:
+**Desired style**
 
-```
+<!-- How do you think _Black_ should format the above snippets: -->
+
+```python
 def f(
     ):
     pass
 ```
 
-**Additional context** Add any other context about the problem here.
+**Additional context**
+
+<!-- Add any other context about the problem here. -->