Skip to content

Commit 39f584c

Browse files
committed
chore(pymarkdown): address findings
1 parent 27f49bd commit 39f584c

File tree

2 files changed

+18
-2
lines changed

2 files changed

+18
-2
lines changed

.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,19 @@ assignees: ''
88
---
99

1010
## Describe the bug
11+
1112
<!-- A clear and concise description of what the bug is. -->
1213

1314
## To reproduce
15+
1416
<!-- Steps to reproduce the behavior: -->
17+
1518
1. cd to '...'
1619
2. Type '....'
1720
3. See problem
1821

1922
## Expected behavior
23+
2024
<!-- A clear and concise description of what you expected to happen. -->
2125

2226
## Versions (please complete the following information)
@@ -26,7 +30,12 @@ assignees: ''
2630
- [ ] bash-completion version, `(IFS=.; echo "${BASH_COMPLETION_VERSINFO[*]}")`:
2731

2832
## Additional context
33+
2934
<!-- Add any other context about the problem here. -->
3035

3136
## Debug trace
32-
<!-- See Troubleshooting section in README.md how to generate a debug trace, copy-paste it into a separate file and attach the file here. -->
37+
38+
<!--
39+
See Troubleshooting section in README.md how to generate a debug trace,
40+
copy-paste it into a separate file and attach the file here.
41+
-->

.github/ISSUE_TEMPLATE/feature_request.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,17 @@ assignees: ''
88
---
99

1010
## Describe the feature/solution
11+
1112
<!-- A clear and concise description of what you want to happen. -->
1213

1314
## Maintenance (please complete the following information)
14-
<!-- See CONTRIBUTING.md, many of the considerations for new completions applies here, too. If upstream has been asked if they'd be interested in shipping the completion instead of us here in bash-completion, include link to the upstream query/issue below. -->
15+
16+
<!--
17+
See CONTRIBUTING.md, many of the considerations for new completions
18+
applies here, too. If upstream has been asked if they'd be interested in
19+
shipping the completion instead of us here in bash-completion, include
20+
link to the upstream query/issue below.
21+
-->
1522

1623
- [ ] This is a request for new completion
1724
- [ ] Link to upstream project query about shipping the completion:

0 commit comments

Comments
 (0)