centersl/gitea-docs
1
0
Fork 0
mirror of https://gitea.com/gitea/docs.git synced 2026-03-27 14:11:03 +07:00
Code Issues Packages Projects Releases Wiki Activity

Update old versions

Browse Source
This commit is contained in:
Lunny Xiao
2024-10-11 00:06:36 -07:00
parent 6fc2decd0c
commit 5f07f6c79a
9 changed files with 18 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/agit-support.md
View File

@@ -35,7 +35,8 @@ git push origin HEAD:refs/for/main
- `title`：PR 的标题
- `topic`：PR 应该打开的分支名称
- `description`：PR 的描述
- `force-push`：确认强制更新目标分支
- `force-push=true`: 是否强制更新目标分支
- 注意: 如果不传值，只用 `-o force-push` 也同样可以正常工作。
下面是另一个高级示例，用于创建一个以 `topic`、`title` 和 `description` 为参数的新 PR，目标分支是 `main`：

3
i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/agit-support.md
View File

@@ -31,7 +31,8 @@ git push origin HEAD:refs/for/master
- `title`：PR 的标题
- `topic`：PR 应该打开的分支名称
- `description`：PR 的描述
- `force-push`：确认强制更新目标分支
- `force-push=true`: 是否强制更新目标分支
- 注意: 如果不传值，只用 `-o force-push` 是无法正常工作的。
下面是另一个高级示例，用于创建一个以 `topic`、`title` 和 `description` 为参数的新 PR，目标分支是 `master`：

3
i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/agit-support.md
View File

@@ -34,7 +34,8 @@ git push origin HEAD:refs/for/master
- `title`：PR 的标题
- `topic`：PR 应该打开的分支名称
- `description`：PR 的描述
- `force-push`：确认强制更新目标分支
- `force-push=true`: 是否强制更新目标分支
- 注意: 如果不传值，只用 `-o force-push` 是无法正常工作的。
下面是另一个高级示例，用于创建一个以 `topic`、`title` 和 `description` 为参数的新 PR，目标分支是 `master`：

3
i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/agit-support.md
View File

@@ -34,7 +34,8 @@ git push origin HEAD:refs/for/main
- `title`：PR 的标题
- `topic`：PR 应该打开的分支名称
- `description`：PR 的描述
- `force-push`：确认强制更新目标分支
- `force-push=true`: 是否强制更新目标分支
- 注意: 如果不传值，只用 `-o force-push` 是无法正常工作的。
下面是另一个高级示例，用于创建一个以 `topic`、`title` 和 `description` 为参数的新 PR，目标分支是 `main`：

3
i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/agit-support.md
View File

@@ -34,7 +34,8 @@ git push origin HEAD:refs/for/main
- `title`：PR 的标题
- `topic`：PR 应该打开的分支名称
- `description`：PR 的描述
- `force-push`：确认强制更新目标分支
- `force-push=true`: 是否强制更新目标分支
- 注意: 如果不传值，只用 `-o force-push` 是无法正常工作的。
下面是另一个高级示例，用于创建一个以 `topic`、`title` 和 `description` 为参数的新 PR，目标分支是 `main`：

3
versioned_docs/version-1.19/usage/agit.md
View File

@@ -33,7 +33,8 @@ The command has the following structure:
- `title`: The PR title
- `topic`: The branch name the PR should be opened for
- `description`: The PR description
- `force-push`: confirm force update the target branch
- `force-push=true`: Specifies whether to force-update the target branch.
- Note: omitting the value and using just `-o force-push` will not work.
Here's another advanced example for creating a new PR targeting `master` with `topic`, `title`, and `description`:

3
versioned_docs/version-1.20/usage/agit.md
View File

@@ -35,7 +35,8 @@ The command has the following structure:
- `title`: The PR title
- `topic`: The branch name the PR should be opened for
- `description`: The PR description
- `force-push`: confirm force update the target branch
- `force-push=true`: Specifies whether to force-update the target branch.
- Note: omitting the value and using just `-o force-push` will not work.
Here's another advanced example for creating a new PR targeting `master` with `topic`, `title`, and `description`:

3
versioned_docs/version-1.21/usage/agit.md
View File

@@ -35,7 +35,8 @@ The command has the following structure:
- `title`: The PR title
- `topic`: The branch name the PR should be opened for
- `description`: The PR description
- `force-push`: confirm force update the target branch
- `force-push=true`: Specifies whether to force-update the target branch.
- Note: omitting the value and using just `-o force-push` will not work.
Here's another advanced example for creating a new PR targeting `main` with `topic`, `title`, and `description`:

3
versioned_docs/version-1.22/usage/agit.md
View File

@@ -37,7 +37,8 @@ The command has the following structure:
- `topic`: The topic of this change. It will become the name of the branch holding the changes waiting for review. This is REQUIRED to trigger a pull request.
- `title`: The PR title (optional but recommended), only used for topics not already having an associated PR.
- `description`: The PR description (optional but recommended), only used for topics not already having an associated PR.
- `force-push`: confirm force update the target branch
- `force-push=true`: Specifies whether to force-update the target branch.
- Note: omitting the value and using just `-o force-push` will not work.
Here's another advanced example for creating a new PR targeting `main` with `topic`, `title`, and `description`: