You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug-report.yaml
+2-2
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ body:
37
37
label: Can you reproduce the bug on the Gitea demo site?
38
38
description: |
39
39
If so, please provide a URL in the Description field
40
-
URL of Gitea demo: https://try.gitea.io
40
+
URL of Gitea demo: https://demo.gitea.com
41
41
options:
42
42
- "Yes"
43
43
- "No"
@@ -74,7 +74,7 @@ body:
74
74
attributes:
75
75
label: How are you running Gitea?
76
76
description: |
77
-
Please include information on whether you built Gitea yourself, used one of our downloads, are using https://try.gitea.io or are using some other package
77
+
Please include information on whether you built Gitea yourself, used one of our downloads, are using https://demo.gitea.com or are using some other package
78
78
Please also tell us how you are running Gitea, e.g. if it is being run from docker, a command-line, systemd etc.
79
79
If you are using a package or systemd tell us what distribution you are using
1. Make sure you are targeting the `main` branch, pull requests on release branches are only allowed for backports.
4
4
2. Make sure you have read contributing guidelines: https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md .
5
-
3. Describe what your pull request does and which issue you're targeting (if any).
6
-
4. It is recommended to enable "Allow edits by maintainers", so maintainers can help more easily.
7
-
5. Your input here will be included in the commit message when this PR has been merged. If you don't want some content to be included, please separate them with a line like `---`.
8
-
6. Delete all these tips before posting.
5
+
3. For documentations contribution, please go to https://gitea.com/gitea/docs
6
+
4. Describe what your pull request does and which issue you're targeting (if any).
7
+
5. It is recommended to enable "Allow edits by maintainers", so maintainers can help more easily.
8
+
6. Your input here will be included in the commit message when this PR has been merged. If you don't want some content to be included, please separate them with a line like `---`.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-3
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ If your issue has not been reported yet, [open an issue](https://github.com/go-g
77
77
and answer the questions so we can understand and reproduce the problematic behavior. \
78
78
Please write clear and concise instructions so that we can reproduce the behavior — even if it seems obvious. \
79
79
The more detailed and specific you are, the faster we can fix the issue. \
80
-
It is really helpful if you can reproduce your problem on a site running on the latest commits, i.e. <https://try.gitea.io>, as perhaps your problem has already been fixed on a current version. \
80
+
It is really helpful if you can reproduce your problem on a site running on the latest commits, i.e. <https://demo.gitea.com>, as perhaps your problem has already been fixed on a current version. \
81
81
Please follow the guidelines described in [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) for your report.
82
82
83
83
Please be kind, remember that Gitea comes at no cost to you, and you're getting free help.
@@ -358,11 +358,12 @@ $REWRITTEN_PR_SUMMARY
358
358
359
359
## Documentation
360
360
361
-
If you add a new feature or change an existing aspect of Gitea, the documentation for that feature must be created or updated in the same PR.
361
+
If you add a new feature or change an existing aspect of Gitea, the documentation for that feature must be created or updated in another PR at [https://gitea.com/gitea/docs](https://gitea.com/gitea/docs).
362
+
**The docs directory on main repository will be removed at some time. We will have a yaml file to store configuration file's meta data. After that completed, configuration documentation should be in the main repository.**
362
363
363
364
## API v1
364
365
365
-
The API is documented by [swagger](http://try.gitea.io/api/swagger) and is based on [the GitHub API](https://docs.github.com/en/rest).
366
+
The API is documented by [swagger](https://gitea.com/api/swagger) and is based on [the GitHub API](https://docs.github.com/en/rest).
For more information and instructions about how to install Gitea, please look at our [documentation](https://docs.gitea.com/).
83
-
If you have questions that are not covered by the documentation, you can get in contact with us on our [Discord server](https://discord.gg/Gitea) or create a post in the [discourse forum](https://discourse.gitea.io/).
83
+
If you have questions that are not covered by the documentation, you can get in contact with us on our [Discord server](https://discord.gg/Gitea) or create a post in the [discourse forum](https://forum.gitea.com/).
84
84
85
85
We maintain a list of Gitea-related projects at [gitea/awesome-gitea](https://gitea.com/gitea/awesome-gitea).
Copy file name to clipboardExpand all lines: README_ZH.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@
18
18
19
19
Gitea 的首要目标是创建一个极易安装,运行非常快速,安装和使用体验良好的自建 Git 服务。我们采用 Go 作为后端语言,这使我们只要生成一个可执行程序即可。并且他还支持跨平台,支持 Linux, macOS 和 Windows 以及各种架构,除了 x86,amd64,还包括 ARM 和 PowerPC。
0 commit comments