]> 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 a crash in ESP where a standalone comment is placed before a dict's value (#3469)
[etc/vim.git] / .github / ISSUE_TEMPLATE / style_issue.md
index a1f7c48011505dd2fde829a3d57970209440fdf5..2e4343a3527be07f0c1f5500f63c9c7ed1b96a33 100644 (file)
@@ -1,30 +1,37 @@
 ---
 name: Style issue
 about: Help us improve the Black style
-title: ''
-labels: design
-assignees: ''
-
+title: ""
+labels: "T: design"
+assignees: ""
 ---
 
 **Describe the style change**
-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:
-```
+<!-- 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:
-```
+
+<!-- How do you think _Black_ should format the above snippets: -->
+
+```python
 def f(
     ):
     pass
 ```
 
 **Additional context**
-Add any other context about the problem here.
+
+<!-- Add any other context about the problem here. -->