Update outdated examples and versions in README
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, github-actions, shell
- Domain
- documentation
Research direction
Update the examples, generated TOC, action and Docker versions, test-count text, tested-on statements, and Combo URL in README. First read the relevant README sections and compare the indentation and test expectations in tests/tests.bats. Keep headings unchanged, then run the tests to confirm the README heading list and updated documentation are correct.
Written by the indexing model from the issue text.
Description
README contains several outdated examples and versions.
Outdated items
- Usage and "Auto insert and update TOC" examples show TOC output in an old
format (2 and 8 space indents). The current default is--indent 3: top-level
entries have no indent, nested ones use 3, 6, ... spaces (seetests/tests.bats). - README's own TOC between
<!--ts-->and<!--te-->was generated by an older
version: its indentation differs from the current output. - "TOC generation with Github Actions" uses
actions/checkout@v2and
stefanzweifel/git-auto-commit-action@v4. The latest releases arev7.0.1and
v7.2.0. - Docker / Public pulls
evkalinin/gh-md-toc:0.7.0. Docker Hub has tags up to
0.10.0, which matchesgh_toc_version. - Tests shows an old run with 6 tests, including "TOC for remote README.md" and
"TOC for mixed README.md (remote/local)", which are commented out now. The suite
has 11 tests. - "Tested on" statements: "macOS High Sierra (gh-md-toc release 0.4.9)" in the
intro and "Ubuntu 14.04/14.10 in bash/zsh" in Dependency. CI runs on
ubuntu-latest. - Combo example has a typo in the URL:
sitemap.sinstead ofsitemap.js.
Notes
tests/tests.batsasserts README's heading list, so headings should stay
unchanged.
- Dominant language
- Shell
- Stars
- 3.3k
- Forks
- 2.7k
- Avg merge
- 19m
- Merged PRs (30d)
- 8
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from ekalinin/github-markdown-toc
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
ekalinin/github-markdown-toc#176 ·
Maintainers usually reply within 1 day
-
[Feature] `--no-code-tag-removal` flag allowing to make removal of backticks in TOC entries optionalPossibly taken A pull request linked to this issue is open or already merged. Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 58/100
ekalinin/github-markdown-toc#153 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ekalinin/github-markdown-toc#152 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ekalinin/github-markdown-toc#141 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
ekalinin/github-markdown-toc#139 ·
Maintainers usually reply within 1 day
All issues in ekalinin/github-markdown-toc
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
mattpocock/skills#1165 ·
-
Statusline badge breaks after a plugin update: the nudge points at the versioned plugin cachePossibly taken @phant0um claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
DietrichGebert/ponytail#1032 ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
bigstack-oss/cubecos#1708 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
omacom/omarchy-mac#693 ·
Maintainers usually reply within 1 day
-
app bug dots mcp windows-os
Difficulty 2/5 Under an hour Newbie friendliness 75/100
openai/codex#50982 · 1 comment ·
Maintainers usually reply within 1 day