Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Failing to create the headers correctly when I use <sub><sub><sub>[Go to Top](#top)</sub></sub></sub>

Open
#40 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
markdown, shell
Domain
cli, documentation

Research direction

Reproduce the issue using the nested header and link example from the report, with README.md as the target context. Start at the TOC-generation entry point and compare the generated list with the expected output; done means the nested markup is excluded from the header text and the resulting anchor is correct.

Written by the indexing model from the issue text.

Description

bug

If I create some headers like:

# Top 

will be generated

## On <sub><sub>[Go to Top](#top)</sub></sub>

side of this page.

Top

will be generated

On Go to Top

side of this page.


It does generates this:

- [Top](#top)
  * [On <sub><sub>[Go to Top](#top)</sub></sub>](#on--sub--sub--go-to-top---top---sub---sub-)

Instead of this:

- [Top](#top)
  * [On](#on-go-to-top)
Dominant language
Shell
Stars
3.3k
Forks
2.7k
Avg merge
20m
Merged PRs (30d)
7

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ekalinin/github-markdown-toc

All issues in ekalinin/github-markdown-toc

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.