Git with a cup of tea, painless self-hosted git service
Mirror for internal git.with.parts use
https://git.with.parts
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
|
|
---
|
|
|
|
|
date: "2018-06-01T19:00:00+02:00"
|
|
|
|
|
title: "合併請求"
|
|
|
|
|
slug: "pull-request"
|
|
|
|
|
weight: 13
|
|
|
|
|
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>
2 years ago
|
|
|
aliases:
|
|
|
|
|
- /zh-tw/pull-request
|
|
|
|
|
menu:
|
|
|
|
|
sidebar:
|
|
|
|
|
parent: "usage"
|
|
|
|
|
name: "合併請求"
|
|
|
|
|
weight: 13
|
|
|
|
|
identifier: "pull-request"
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# 合併請求
|
|
|
|
|
|
|
|
|
|
## 「還在進行中（WIP）」的合併請求
|
|
|
|
|
|
|
|
|
|
將合併請求標記為還在進行中（Work In Progress, WIP）可避免意外地被合併。
|
|
|
|
|
要將合併請求標記為還在進行中請在標題中使用 `WIP:` 或 `[WIP]` 前綴（不分大小寫）。這些值可在您的 `app.ini` 中設定：
|
|
|
|
|
|
|
|
|
|
```ini
|
|
|
|
|
[repository.pull-request]
|
|
|
|
|
WORK_IN_PROGRESS_PREFIXES=WIP:,[WIP]
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
網頁提示會使用第一個值作為範例。
|
|
|
|
|
|
|
|
|
|
## 合併請求範本
|
|
|
|
|
|
|
|
|
|
您可以在[問題與合併請求範本](issue-pull-request-templates)找到更多關於合併請求範本的資訊。
|
