domi/forgejo-domi
1
0
Fork 0
forked from forgejo/forgejo
Code Pull requests Activity
14942 commits 12 branches 216 tags 565 MiB
Commit graph

14 commits

Author SHA1 Message Date
HesterG
c23ab427e1
Change branch name from master to main in some documents' links () () 
Backport 

As title. And needs to backport to 1.19
 2023-06-08 04:31:55 -04:00
HesterG
37b73b3337
Add Chinese docs for help, contribution and development () () 
Backport , partially backport 
(`docs/content/doc/help/faq.zh-cn.md` file)

Part of backport has already done by 

Also backport  to avoid "deadlock"

---------

Co-authored-by: Zettat123 <zettat123@gmail.com>
 2023-05-31 14:12:37 +08:00
Giteabot
8a6a1143a4
Remove reference to caddy v1 in docs () () 
Backport  by @techknowlogick

caddy v1 is loong eol. v2 should be used.

Co-authored-by: techknowlogick <techknowlogick@gitea.io>
 2023-05-28 05:34:50 -04:00
Lunny Xiao
e7757aa4be
Remove unnecessary prefix usage () 
Since now all articles have a class, the `Usage:` is unnecessary. This
PR will remove them.
 2023-05-24 00:34:31 +08:00
Giteabot
aa984f21fa
Fix docs documenting invalid @every for OLDER_THAN cron settings () () 
Backport  by @yardenshoham

Looks like a copy-paste leftover

- Fixes 

Co-authored-by: Yarden Shoham <git@yardenshoham.com>
 2023-05-13 23:47:56 +08:00
Giteabot
cc7a4f17e0
Don't set meta theme-color by default () () 
Backport  by @silverwind

Fixes https://github.com/go-gitea/gitea/issues/24321. By not setting
this meta tag, Safari will use body color for chrome and out-of-viewport
areas, which looks much better then static mismatching green.

As per
[MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta/name/theme-color)
it's really only Apple browsers who still support this tag, most others
have dropped support.
 
Before:
<img width="347" alt="Screenshot 2023-04-25 at 19 59 13"
src="https://user-images.githubusercontent.com/115237/234363180-0fe667ef-5469-4f5f-b31a-c9d73aff10ac.png">

After:
<img width="361" alt="Screenshot 2023-04-25 at 20 00 00"
src="https://user-images.githubusercontent.com/115237/234363185-e2d2b62f-0133-4316-944d-b614ffb84eb0.png">

Co-authored-by: silverwind <me@silverwind.io>
 2023-04-26 01:33:15 -04:00
Giteabot
8d88f148d7
docs: make the required backticks in email password more explicit () () 
Backport  by @teauxfu

updated the example config to make the needed backticks around the
password more obvious

Co-authored-by: alex <alexmw777@gmail.com>
 2023-04-04 15:06:54 -04:00
Giteabot
7bfab90a8f
docs: fix typo () () 
Backport  by @teauxfu

fixes a minor typo in the email templates page

Co-authored-by: alex <alexmw777@gmail.com>
 2023-04-04 18:13:09 +02:00
Lunny Xiao
1a8da2e08f
Update docs markdown file weight to make it clear () () 
backport
2023-04-04 11:27:38 -04:00
Giteabot
1886bd6a01
Rename actions unit to repo.actions and add docs for it () () 
Backport  by @wolfogre

I neglected that the `NameKey` of `Unit` is not only for translation,
but also configuration. So it should be `repo.actions` to maintain
consistency.

## ⚠️ BREAKING ⚠️

If users already use `actions.actions` in `DISABLED_REPO_UNITS` or
`DEFAULT_REPO_UNITS`, it will be treated as an invalid unit key.

Co-authored-by: Jason Song <i@wolfogre.com>
 2023-04-03 12:54:36 +02:00
wxiaoguang
d15f20b2d2
Add ONLY_SHOW_RELEVANT_REPOS back, fix explore page bug, make code more strict () () 
Follow 

After I eat my own dogfood, I would say that
ONLY_SHOW_RELEVANT_REPOS=false is necessary for many private/enterprise
instances, because many private repositories do not have
"description/topic", users just want to search by their names.

This PR also adds `PageIsExploreRepositories` check, to make code more
strict, because the `search` template is shared for different purpose.

And during the test, I found a bug that the "Search" button didn't
respect the "relevant" parameter, so this PR fixes the bug by the way
together.
 2023-03-30 09:09:22 -05:00
wxiaoguang
b73d1ac1eb
Make minio package support legacy MD5 checksum () () 
Backport  (no source code conflict, only some unrelated
docs/test-ini conflicts)

Some storages like:

 * https://developers.cloudflare.com/r2/api/s3/api/
 * https://www.backblaze.com/b2/docs/s3_compatible_api.html

They do not support "x-amz-checksum-algorithm" header

But minio recently uses that header with CRC32C by default. So we have
to tell minio to use legacy MD5 checksum.
 2023-03-29 00:02:13 +08:00
Giteabot
a28863bff7
Fix codeblocks in the cheat sheet () () 
Backport  by @SuperSandro2000

Conflicts fixed by Andrew Thornton <art27@cantab.net>

Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
Co-authored-by: Andrew Thornton <art27@cantab.net>
 2023-03-23 16:50:56 -04:00
Lunny Xiao
162f2841d0
Rename develop -> development, contribute -> contributing, administer -> administration () 
backport  

To make versioned documentation less surprising, 1.19 should have the
same technology.
 2023-03-23 15:44:09 -05:00