loading up the forgejo repo on tangled to test page performance
Change the default branch in the agit docs (#27621)
authored by
Nanguan Lin
and committed by
GitHub
e29e40d1
76a85a4c
+6
-6
+3
-3
docs/content/usage/agit-support.en-us.md
+3
-3
docs/content/usage/agit-support.en-us.md
···
26
26
The following example illustrates this:
27
27
28
28
```shell
29
-
git push origin HEAD:refs/for/master
29
+
git push origin HEAD:refs/for/main
30
30
```
31
31
32
32
The command has the following structure:
···
42
42
- `description`: The PR description
43
43
- `force-push`: confirm force update the target branch
44
44
45
-
Here's another advanced example for creating a new PR targeting `master` with `topic`, `title`, and `description`:
45
+
Here's another advanced example for creating a new PR targeting `main` with `topic`, `title`, and `description`:
46
46
47
47
```shell
48
-
git push origin HEAD:refs/for/master -o topic="Topic of my PR" -o title="Title of the PR" -o description="# The PR Description\nThis can be **any** markdown content.\n- [x] Ok"
48
+
git push origin HEAD:refs/for/main -o topic="Topic of my PR" -o title="Title of the PR" -o description="# The PR Description\nThis can be **any** markdown content.\n- [x] Ok"
49
49
```
+3
-3
docs/content/usage/agit-support.zh-cn.md
+3
-3
docs/content/usage/agit-support.zh-cn.md
···
26
26
下面的示例说明了这一点：
27
27
28
28
```shell
29
-
git push origin HEAD:refs/for/master
29
+
git push origin HEAD:refs/for/main
30
30
```
31
31
32
32
该命令的结构如下：
···
42
42
- `description`：PR 的描述
43
43
- `force-push`：确认强制更新目标分支
44
44
45
-
下面是另一个高级示例，用于创建一个以 `topic`、`title` 和 `description` 为参数的新 PR，目标分支是 `master`：
45
+
下面是另一个高级示例，用于创建一个以 `topic`、`title` 和 `description` 为参数的新 PR，目标分支是 `main`：
46
46
47
47
```shell
48
-
git push origin HEAD:refs/for/master -o topic="Topic of my PR" -o title="Title of the PR" -o description="# The PR Description\nThis can be **any** markdown content.\n- [x] Ok"
48
+
git push origin HEAD:refs/for/main -o topic="Topic of my PR" -o title="Title of the PR" -o description="# The PR Description\nThis can be **any** markdown content.\n- [x] Ok"
49
49
```