2021-01-29 00:57:58 +00:00
|
|
|
---
|
|
|
|
|
date: "2018-05-21T15:00:00+00:00"
|
|
|
|
|
title: "取得協助"
|
Refactor docs (#23752)
This was intended to be a small followup for
https://github.com/go-gitea/gitea/pull/23712, but...here we are.
1. Our docs currently use `slug` as the entire URL, which makes
refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712).
Instead, this PR attempts to make future refactoring easier by using
slugs as an extension of the section. (Hugo terminology)
- What the above boils down to is this PR attempts to use directory
organization as URL management. e.g. `usage/comparison.en-us.md` ->
`en-us/usage/comparison/`, `usage/packages/overview.en-us.md` ->
`en-us/usage/packages/overview/`
- Technically we could even remove `slug`, as Hugo defaults to using
filename, however at least with this PR it means `slug` only needs to be
the name for the **current file** rather than an entire URL
2. This PR adds appropriate aliases (redirects) for pages, so anything
on the internet that links to our docs should hopefully not break.
3. A minor nit I've had for a while, renaming `seek-help` to `support`.
It's a minor thing, but `seek-help` has a strange connotation to it.
4. The commits are split such that you can review the first which is the
"actual" change, and the second is added redirects so that the first
doesn't break links elsewhere.
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-04-28 03:33:41 +00:00
|
|
|
slug: "support"
|
2023-07-26 04:53:13 +00:00
|
|
|
sidebar_position: 20
|
2021-01-29 00:57:58 +00:00
|
|
|
toc: false
|
|
|
|
|
draft: false
|
Refactor docs (#23752)
This was intended to be a small followup for
https://github.com/go-gitea/gitea/pull/23712, but...here we are.
1. Our docs currently use `slug` as the entire URL, which makes
refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712).
Instead, this PR attempts to make future refactoring easier by using
slugs as an extension of the section. (Hugo terminology)
- What the above boils down to is this PR attempts to use directory
organization as URL management. e.g. `usage/comparison.en-us.md` ->
`en-us/usage/comparison/`, `usage/packages/overview.en-us.md` ->
`en-us/usage/packages/overview/`
- Technically we could even remove `slug`, as Hugo defaults to using
filename, however at least with this PR it means `slug` only needs to be
the name for the **current file** rather than an entire URL
2. This PR adds appropriate aliases (redirects) for pages, so anything
on the internet that links to our docs should hopefully not break.
3. A minor nit I've had for a while, renaming `seek-help` to `support`.
It's a minor thing, but `seek-help` has a strange connotation to it.
4. The commits are split such that you can review the first which is the
"actual" change, and the second is added redirects so that the first
doesn't break links elsewhere.
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-04-28 03:33:41 +00:00
|
|
|
aliases:
|
|
|
|
|
- /zh-tw/seek-help
|
2021-01-29 00:57:58 +00:00
|
|
|
menu:
|
|
|
|
|
sidebar:
|
|
|
|
|
parent: "help"
|
|
|
|
|
name: "取得協助"
|
2023-07-26 04:53:13 +00:00
|
|
|
sidebar_position: 20
|
Refactor docs (#23752)
This was intended to be a small followup for
https://github.com/go-gitea/gitea/pull/23712, but...here we are.
1. Our docs currently use `slug` as the entire URL, which makes
refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712).
Instead, this PR attempts to make future refactoring easier by using
slugs as an extension of the section. (Hugo terminology)
- What the above boils down to is this PR attempts to use directory
organization as URL management. e.g. `usage/comparison.en-us.md` ->
`en-us/usage/comparison/`, `usage/packages/overview.en-us.md` ->
`en-us/usage/packages/overview/`
- Technically we could even remove `slug`, as Hugo defaults to using
filename, however at least with this PR it means `slug` only needs to be
the name for the **current file** rather than an entire URL
2. This PR adds appropriate aliases (redirects) for pages, so anything
on the internet that links to our docs should hopefully not break.
3. A minor nit I've had for a while, renaming `seek-help` to `support`.
It's a minor thing, but `seek-help` has a strange connotation to it.
4. The commits are split such that you can review the first which is the
"actual" change, and the second is added redirects so that the first
doesn't break links elsewhere.
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-04-28 03:33:41 +00:00
|
|
|
identifier: "support"
|
2021-01-29 00:57:58 +00:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# 取得協助
|
|
|
|
|
|
|
|
|
|
- [Discord 聊天室](https://discord.gg/Gitea)
|
|
|
|
|
- [Discourse 討論區](https://discourse.gitea.io/)
|
|
|
|
|
|
|
|
|
|
**備註：** 尋求支援時，若能先備妥下列資訊將可讓提供協助的人能快速地分析您的問題：
|
|
|
|
|
|
|
|
|
|
1. 您的 `app.ini` (必要時清除掉任何機密資訊)
|
|
|
|
|
2. `gitea.log` (以及任何有關的日誌檔案)
|
2022-07-28 01:22:47 +00:00
|
|
|
- 例：如果錯誤和資料庫相關，提供 `xorm.log` 可能會有幫助
|
2021-01-29 00:57:58 +00:00
|
|
|
3. 您看到的任何錯誤訊息
|
2021-12-03 13:04:32 +00:00
|
|
|
4. 儘可能地在 [try.gitea.io](https://try.gitea.io) 觸發您的問題並記下步驟，以便其他人能重現那個問題。
|
2022-07-28 01:22:47 +00:00
|
|
|
- 這將讓我們更有機會快速地找出問題的根源並解決它。
|
2023-08-27 11:59:12 +00:00
|
|
|
5. 堆棧跟踪，[請參考英文文檔](https://docs.gitea.com/help/support)
|
2021-01-29 00:57:58 +00:00
|
|
|
|
|
|
|
|
## 錯誤回報
|
2021-12-03 13:04:32 +00:00
|
|
|
|
|
|
|
|
如果您發現錯誤，請到 [GitHub 的 Issue](https://github.com/go-gitea/gitea/issues) 回報。
|
