-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve docs about register/run as a service #27461
Conversation
@@ -36,7 +38,7 @@ If you use SQLite3, change the `PATH` to include the full path: | |||
PATH = c:/gitea/data/gitea.db | |||
``` | |||
|
|||
# Register as a Windows Service | |||
## Register as a Windows service |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting that we have a <h1>
and <h2>
with the same text…
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually the rule is partially enabled. It does allow same heading at different levels (allow_different_nesting
). If I forbid that, it finds these:
docs/content/administration/cmd-embedded.en-us.md:104 MD024/no-duplicate-heading/no-duplicate-header Multiple headings with the same content [Context: "### Example"]
docs/content/administration/cmd-embedded.zh-cn.md:86 MD024/no-duplicate-heading/no-duplicate-header Multiple headings with the same content [Context: "### 示例"]
docs/content/installation/database-preparation.en-us.md:187 MD024/no-duplicate-heading/no-duplicate-header Multiple headings with the same content [Context: "### PostgreSQL"]
docs/content/installation/database-preparation.zh-cn.md:185 MD024/no-duplicate-heading/no-duplicate-header Multiple headings with the same content [Context: "### PostgreSQL"]
docs/content/installation/database-preparation.zh-cn.md:253 MD024/no-duplicate-heading/no-duplicate-header Multiple headings with the same content [Context: "### MySQL"]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In any case, I think it should be forbidden because the anchors will not work correctly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems docasaurus can somewhat deal with it:
https://docs.gitea.com/administration/cmd-embedded#example
https://docs.gitea.com/administration/cmd-embedded#example-1
Issue is if the first example is deleted, the link that previously pointed to it will now point to the other example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#27500 will fix the cases on main branch. I recommend this PR to adapt.
Duplicate MD header should be removed, #27500 will enforce this. |
OK. Will remove duplicate headers and wait for that PR. |
Duplicate headers in a single Markdown document are problemlematic because the auto-generated links won't be stable. Enable this rule with no exceptions which is also the default of `markdownlint`. For example: ```md # A ## Example # B ## Example ``` Docasaurus will generated `example` and `example-1` links for this. If the first heading is altered, the link `example` will unexpectedly move to the second example heading. Ref: #27461 (comment)
Duplicate headers in a single Markdown document are problemlematic because the auto-generated links won't be stable. Enable this rule with no exceptions which is also the default of `markdownlint`. For example: ```md # A ## Example # B ## Example ``` Docasaurus will generated `example` and `example-1` links for this. If the first heading is altered, the link `example` will unexpectedly move to the second example heading. Ref: go-gitea#27461 (comment)
Backport #27500 by @silverwind Duplicate headers in a single Markdown document are problemlematic because the auto-generated links won't be stable. Enable this rule with no exceptions which is also the default of `markdownlint`. For example: ```md # A ## Example # B ## Example ``` Docasaurus will generated `example` and `example-1` links for this. If the first heading is altered, the link `example` will unexpectedly move to the second example heading. Ref: #27461 (comment) Co-authored-by: silverwind <me@silverwind.io>
* giteaofficial/main: Respect SSH.KeygenPath option when calculating ssh key fingerprints (go-gitea#27536) Remove max-width and add hide text overflow (go-gitea#27359) Fix `environment-to-ini` inherited key bug (go-gitea#27543) Improve docs about register/run as a service (go-gitea#27461) api: GetPullRequestCommits: return file list (go-gitea#27483) switch to using official AWS step in release nightly (go-gitea#27532) Improve file history UI and fix URL escaping bug (go-gitea#27531) Improve dropdown's behavior when there is a search input in menu (go-gitea#27526) Simplify `contrib/backport` (go-gitea#27520) Add docs section for sub-paths with the container registry (go-gitea#27505) Document our new labeling strategy (go-gitea#27523) [skip ci] Updated translations via Crowdin Restore warning commit status (go-gitea#27504) Update labeler to match new labeling system (go-gitea#27525) Apply to become a maintainer (go-gitea#27522) Remove unnecessary desc for openssh key cron task (go-gitea#27515) Tweak labeler config (go-gitea#27502) Add hover background to wiki list page (go-gitea#27507) [FIX] missing ctx in new_form (go-gitea#27514)
As title