Footnotes now supported in Markdown fields
Open
Nobody has claimed this yet.
markdown
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
This ...
Footnotes now supported in Markdown fields[^1].
[^1]: [Blog post](https://github.blog/changelog/2021-09-30-footnotes-now-supported-in-markdown-fields/)
yields this ...
Footnotes now supported in Markdown fields[^1].
[^1]: Blog post
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file, test, or entry point. First clarify which Markdown field or resource should change and identify its location; completion should specify the documentation update or support behavior expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100