[ BUG ] Wrong filename in Github Action (the trailing ".md" should be removed)
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 35/100
Direzione di ricerca
Start with the gh-md-toc script downloaded and invoked by the workflow, using the reported server.md example as the reproduction. Check how links are generated for headings in wiki files and verify that the output uses only the heading anchor, without the .md filename, while remaining suitable for the generated site.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
To start with: thank you for this great Markdown enhancement!
Describe the bug
I added a github action in the graphql-maven-plugin-project'wiki.
The issue is that the URL in the generated TOC doesn't work.
You can check on this file
Expected behavior
The generated link is:
* [GraphQL Maven Plugin (server mode usage)](server.md#graphql-maven-plugin-server-mode-usage)
But it should be:
* [GraphQL Maven Plugin (server mode usage)](#graphql-maven-plugin-server-mode-usage)
Without the filename at all. This insures that the link will work:
- In the github wiki (where the URL is
https://github.com/graphql-java-generator/graphql-maven-plugin-project/wiki/server) - In the site generated by maven (where the URL is
https://graphql-maven-plugin-project.graphql-java-generator.com/server.html)- The filename ends with
.htmlhere
- The filename ends with
Perhaps there is a parameter to manage that, but I did not find it.
Environment (please complete the following information):
I'm execution the github action with this action file:
# This is a basic workflow to help you get started with Actions
name: Wiki TOC
# Controls when the action will run.
on:
# Triggers the workflow on any change on the wiki (on the master branch)
#gollum: # This is triggered each time a file is changed on the wiki, including when the this script automatically run!
# Below: push on the wiki, for the master branch
#push:
# paths:
# - 'wiki/**'
# branches:
# - master
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
# This workflow contains a single job called "toc"
toc:
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
- uses: actions/checkout@v2
with:
repository: ${{github.repository}}.wiki
- run: |
ls
curl https://raw.githubusercontent.com/ekalinin/github-markdown-toc/master/gh-md-toc -o gh-md-toc
chmod a+x gh-md-toc
./gh-md-toc --insert --no-backup *.md
- uses: stefanzweifel/git-auto-commit-action@v4
with:
commit_message: Auto update markdown TOC
- Lingua principale
- Shell
- Stelle
- 3.3k
- Fork
- 2.7k
- Merge medio
- 20m
- PR unite (30g)
- 7
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di ekalinin/github-markdown-toc
-
Update bats version in CIAperta
Difficoltà 1/5 1-3 ore Idoneità per principianti 78/100
ekalinin/github-markdown-toc#176 ·
-
documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
ekalinin/github-markdown-toc#165 ·
-
[Feature] `--no-code-tag-removal` flag allowing to make removal of backticks in TOC entries optionalApertaenhancement
Difficoltà 3/5 1-2 giorni Idoneità per principianti 58/100
ekalinin/github-markdown-toc#153 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
ekalinin/github-markdown-toc#152 · 1 reazione ·
-
bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
ekalinin/github-markdown-toc#141 ·
Tutte le issue di ekalinin/github-markdown-toc
Issue simili
-
Update vtm to 2026.9.28Apertapackage-update
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
oSoWoSo/vOid_Community_repOsitory#207 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
alunduil/alunduil-chezmoi#815 ·
I maintainer di solito rispondono entro 1 giorno
-
good first issue new package
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
wimpysworld/deb-get#2035 ·
I maintainer di solito rispondono entro 1 giorno
-
automation documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
termux/termux-packages#32085 ·
I maintainer di solito rispondono entro 1 giorno