@@ -47,15 +47,15 @@ When referencing a label in a GitHub issue or discussion, it will be useful to
4747
4848To link to a label in GitHub Markdown, use the following syntax:
4949
50- ```
50+ ```
5151[label name](https://github.com/username/repository/labels/label-name)
5252```
5353
5454### Example
5555
5656For example, to link to the "hackathon" label in the nsidc/earthaccess repository, you would use the following syntax:
5757
58- ```
58+ ```
5959[hackathon](https://github.com/nsidc/earthaccess/labels/hackathon)
6060```
6161
@@ -80,7 +80,7 @@ When closing an issue as not planned, keep the following best practices in mind:
8080- Offer alternative solutions or workarounds, if possible.
8181- Link to relevant documentation or resources, if applicable.
8282
83- ## Discussions vs Issues
83+ ## Discussions vs Issues
8484
8585This section would cover the guidelines for when to use discussions versus issues, and how to migrate between them.
8686
@@ -100,7 +100,7 @@ Issues are used for:
100100- Tracking progress on specific tasks or projects.
101101- Requesting changes or improvements.
102102
103- ### When to Migrate
103+ ### When to Migrate
104104
105105Migrate a discussion to an issue when:
106106
@@ -121,10 +121,10 @@ Migrate an issue to a discussion when:
121121flowchart TD
122122 %%{init: {"flowchart": {"htmlLabels": false}} }%%
123123 classDef default font-size:32pt;
124- start{"`Followed
125- issue
124+ start{"`Followed
125+ issue
126126 template?`"}
127- start ==NO==> close1[Change
127+ start ==NO==> close1[Change
128128 to draft and ask to follow template]
129129 start == YES ==> dupe{Is duplicate?}
130130 dupe == YES ==> close2[Close and point to duplicate]
@@ -147,10 +147,3 @@ flowchart TD
147147 linkStyle default stroke:black,stroke-width:2px,font-size:24pt;
148148
149149```
150-
151-
152-
153-
154-
155-
156-
0 commit comments