crapStone
5374d29aa9
Add gist to comparison ( #28809 )
...
This PR adds a section to the documentation that links to the project
[Opengist](https://github.com/thomiceli/opengist ) on GitHub.
The feature was proposed in #16670 but didn't resonate well with the
maintainers.
2024-01-15 23:37:32 +01:00
Exploding Dragon
ba4d0b8ffb
Support for grouping RPMs using paths ( #26984 )
...
The current rpm repository places all packages in the same repository,
and different systems (el7,f34) may hit packages that do not belong to
this distribution ( #25304 ) , which now supports grouping of rpm.
Fixes #25304 .
Fixes #27056 .
Refactor: [#25866 ](https://github.com/go-gitea/gitea/pull/25866 )
2024-01-12 03:16:05 +00:00
wxiaoguang
2df7563f31
Recommend/convert to use case-sensitive collation for MySQL/MSSQL ( #28662 )
...
Mainly for MySQL/MSSQL.
It is important for Gitea to use case-sensitive database charset
collation. If the database is using a case-insensitive collation, Gitea
will show startup error/warning messages, and show the errors/warnings
on the admin panel's Self-Check page.
Make `gitea doctor convert` work for MySQL to convert the collations of
database & tables & columns.
* Fix #28131
## ⚠️ BREAKING ⚠️
It is not quite breaking, but it's highly recommended to convert the
database&table&column to a consistent and case-sensitive collation.
2024-01-10 11:03:23 +00:00
wxiaoguang
7215224112
Improve frontend guideline ( #28711 )
...
It has been a consensus for long time during reviewing: "avoiding inline
styles as much as possible".
2024-01-07 01:14:10 +08:00
Kyle D
54acf7b0d4
Normalize oauth email username ( #28561 )
2024-01-03 18:48:20 -06:00
Yarden Shoham
cdc33b29a0
Add global setting how timestamps should be rendered ( #28657 )
...
- Resolves https://github.com/go-gitea/gitea/issues/22493
- Related to https://github.com/go-gitea/gitea/issues/4520
Some admins prefer all timestamps to display the full date instead of
relative time. They can do that now by setting
```ini
[ui]
PREFERRED_TIMESTAMP_TENSE = absolute
```
This setting is set to `mixed` by default, allowing dates to render as
"5 hours ago". Here are some screenshots of the UI with this setting set
to `absolute`:
---------
Signed-off-by: Yarden Shoham <git@yardenshoham.com>
Co-authored-by: delvh <dev.lh@web.de>
2024-01-02 09:25:30 +08:00
silverwind
ce55a74374
Update JS dependencies ( #28537 )
...
- Update all JS dependencies excluding mcaptcha (breaking changes) and
stylelint (plugin not compatible with v16)
- Regenerate SVGs
- Update markdownlint rule names
- Fix one issue of heading in markdown discovered during lint
- Update for monaco options renames
- Fix stylelint rule length-zero-no-unit for custom properties
- Tested editor, swagger, sorting, vue, lint
2023-12-30 05:29:03 +00:00
wxiaoguang
19b1b698c9
Improve document for ARTIFACT_RETENTION_DAYS ( #28646 )
...
Follow #28626
2023-12-29 06:44:58 +00:00
wxiaoguang
19c45dd479
Improve 1.22 document for Database Preparation ( #28643 )
...
Fix #28247
2023-12-29 05:42:22 +00:00
Denys Konovalov
6c133b9fe0
switch destination directory for apt signing keys ( #28639 )
...
According to [Debian
docs](https://wiki.debian.org/DebianRepository/UseThirdParty ):
> The certificate MUST NOT be placed in /etc/apt/trusted.gpg.d or loaded
by apt-key add.
> ...
> If future updates to the certificate will be managed by an apt/dpkg
package as recommended below, then it SHOULD be downloaded into
/usr/share/keyrings using the same filename that will be provided by the
package. If it will be managed locally , it SHOULD be downloaded into
/etc/apt/keyrings instead.
> ...
> A sources.list entry SHOULD have the signed-by option set.
2023-12-28 22:08:59 +01:00
Gerd Katzenbeisser
4d1277c0cb
Extend description for ARTIFACT_RETENTION_DAYS ( #28626 )
...
Make it clear that this value is just a default value and that every
artifact can have it's own value.
2023-12-28 10:11:44 +00:00
Volodymyr Stelmashchuk
0e9c988373
Update repo-mirror.en-us.md ( #28612 )
...
Add small changes to the doc. The workflow scope require for push code
to github mirror in case the project use the github action compatibility
ui.
2023-12-27 00:36:11 +08:00
wxiaoguang
b41925cee3
Refactor CORS handler ( #28587 )
...
The CORS code has been unmaintained for long time, and the behavior is
not correct.
This PR tries to improve it. The key point is written as comment in
code. And add more tests.
Fix #28515
Fix #27642
Fix #17098
2023-12-25 20:13:18 +08:00
Lunny Xiao
177cea7c70
Make offline mode as default to no connect external avatar service by default ( #28548 )
...
To keep user's privacy, make offline mode as true by default.
Users can still change it from installation ui and app.ini
2023-12-21 07:42:16 +00:00
Rui Chen
caceb43313
feat: bump dessant/lock-threads and actions/setup-go to use nodejs20 runtime ( #28565 )
...
Update more actions to use nodejs20 runtime and also update the docs for
checkout action usage.
similar to:
- #27836
- #27096
---------
Signed-off-by: Rui Chen <rui@chenrui.dev>
2023-12-21 13:31:04 +08:00
Lunny Xiao
3d98d99e27
Update actions document about comparsion as Github Actions ( #28560 )
2023-12-20 20:12:25 +00:00
Lunny Xiao
e7cb8da2a8
Always enable caches ( #28527 )
...
Nowadays, cache will be used on almost everywhere of Gitea and it cannot
be disabled, otherwise some features will become unaviable.
Then I think we can just remove the option for cache enable. That means
cache cannot be disabled.
But of course, we can still use cache configuration to set how should
Gitea use the cache.
2023-12-19 09:29:05 +00:00
wxiaoguang
20929edc99
Add option to disable ambiguous unicode characters detection ( #28454 )
...
* Close #24483
* Close #28123
* Close #23682
* Close #23149
(maybe more)
2023-12-17 14:38:54 +00:00
Kyle D
b8490d59de
Update docs for DISABLE_QUERY_AUTH_TOKEN ( #28485 )
...
As described
[here](https://github.com/go-gitea/gitea/pull/28390#issuecomment-1857553331 ).
2023-12-15 21:54:35 -05:00
wxiaoguang
047c69bd85
Improve CLI code and descriptions ( #28482 )
...
* Close #28444
* Actually, it doesn't need to use that trick because it looks like it
is not necessary, no user really needs it
* Remove the hidden (legacy) "doctor" subcommand and update documents
* Fix "actions" usage
2023-12-15 15:49:01 +00:00
CaiCandong
8c91e31540
Fix Chinese translation of config cheat sheet[API] ( #28472 )
2023-12-15 00:00:04 +08:00
wxiaoguang
e85db6c8c3
Fix documents for "custom/public/assets/" ( #28465 )
...
Fix #28463
2023-12-14 08:52:16 +00:00
David Hulick
73047854c0
docs: Update group membership fields to match application. ( #28175 )
...
Several fields in the "Verify group membership in LDAP" docs were
confusingly titled when compared to the actual fields in the
application, this change rectifies that by matching the docs to the
fields already present in gitea.
Signed-off-by: David Hulick <dave.hulick@gmail.com>
2023-12-13 07:14:37 +00:00
yp05327
1ae33e0bad
Fix links in docs ( #28302 )
...
Close #28287
## How to test it in local
convert Makefile L34 into:
```
cd .tmp/upstream-docs && git clean -f && git reset --hard && git fetch origin pull/28302/head:pr28302 && git switch pr28302
```
2023-12-01 19:42:42 +08:00
yp05327
0a0e8200ec
Fix links in docs ( #28234 )
...
Follow #28191
Changes:
- `(doc/administration/config-cheat-sheet.md` is incorrect:
- remove `../../`
2023-11-27 00:34:40 -05:00
CodeShakingSheep
80217cacfc
Docs: Replace deprecated IS_TLS_ENABLED mailer setting in email setup ( #28205 )
...
In the [docs for email
setup](https://docs.gitea.com/administration/email-setup )
`mailer.IS_TLS_ENABLED` is mentioned which was replaced by
`mailer.PROTOCOL` in release 1.18.0 according to
https://blog.gitea.com/release-of-1.18.0/ . This change wasn't reflected
in the docs for email setup. I just replaced the deprecated mailer
setting.
2023-11-25 10:16:29 +08:00
yp05327
ad9aac3975
Fix some incorrect links in docs ( #28191 )
...
https://gitea.com/gitea/gitea-docusaurus/actions/runs/661/jobs/0#jobstep-9-39
I noticed that there are many warning logs in building docs.
It is causing 404 in docs.gitea.com now, so we need to fix it.
And there are also some other problems in v1.19 which can not be done in
this PR.
ps: Are there any good methods to test this in local?
2023-11-24 13:57:09 +00:00
yp05327
2d9b91aa24
Fix the description about the default setting for action in quick start document ( #28160 )
...
Since #27054 , Actions are enabled by default. so we should also edit the
document. 😃
ps: I think this should be backport to 1.21.0.
2023-11-22 02:11:22 +00:00
John Olheiser
30b46fb6fa
Update docs for docusaurus v3 ( #28125 )
...
Updates the docs for usage with docusaurus v3
Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-11-20 00:25:47 -05:00
Denys Konovalov
816e46ee7c
add skip ci functionality ( #28075 )
...
Adds the possibility to skip workflow execution if the commit message
contains a string like [skip ci] or similar.
The default strings are the same as on GitHub, users can also set custom
ones in app.ini
Reference:
https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs
Close #28020
2023-11-18 13:37:08 +02:00
Nanguan Lin
0678c82265
Change default size of issue/pr attachments and repo file ( #27946 )
...
As title. Some attachments and file sizes can easily be larger than
these limits
2023-11-13 14:19:22 +00:00
6543
603573366a
Add Profile Readme for Organisations ( #27955 )
...
https://blog.gitea.com/release-of-1.20.0/#-user-profile-readme-23260
(#23260 ) did introduce Profile Readme for Users.
This makes it usable for Organisations:
---
*Sponsored by Kithara Software GmbH*
---------
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
2023-11-09 14:05:52 +00:00
6543
16ba16dbe9
Allow to set explore page default sort ( #27951 )
...
as title
---
*Sponsored by Kithara Software GmbH*
2023-11-09 10:11:45 +00:00
6543
8ef169a173
Document REACTION_MAX_USER_NUM setting option ( #27954 )
...
4a0103fa29/modules/setting/ui.go (L24)4a0103fa29/modules/setting/ui.go (L77)
2023-11-08 01:50:31 +01:00
Nanguan Lin
1e25c15d98
Remove known issue section in Gitea Actions Doc ( #27930 )
...
The bug has been fixed for several months in the
`docker/build-push-action`
The fix commit is
[d8823bfaed](d8823bfaed
2023-11-06 22:45:37 +08:00
Moritz Poldrack
9b6e77c489
refactor postgres connection string building ( #27723 )
...
This patchset changes the connection string builder to use net.URL and
the host/port parser to use the stdlib function for splitting host from
port. It also adds a footnote about a potentially required portnumber
for postgres UNIX sockets.
Fixes: #24552
2023-11-01 18:00:20 +00:00
nodiscc
665d12cf84
doc: actions/act-runner: document running as a systemd service ( #27844 )
...
This documents running `act-runner` as a systemd service under a
dedicated user account.
2023-11-01 23:14:40 +08:00
Lunny Xiao
6ca234a356
Fix wrong relative path on obtain token from command line ( #27850 )
...
Caused by #27845
2023-10-30 23:31:09 -04:00
nodiscc
a18ecaed61
doc: actions/act-runner: document obtaining a runner registration token from gitea CLI ( #27845 )
2023-10-30 19:28:02 -04:00
HoshinoRei
9b991f2947
Fix an indentation in the Chinese documentation of Act Runner ( #27730 )
...
In the [English
document](https://docs.gitea.com/1.21/usage/actions/act-runner#configuring-cache-when-starting-a-runner-using-docker-image ),
there is indentation here, but there is no indentation in the Chinese
document.
2023-10-22 19:37:56 +08:00
MiloCubed
2f2ca8c940
[docs] Add note that PROTOCOL config is case-sensitive ( #25685 )
...
See [issue on
gitea.com](https://gitea.com/gitea/gitea-docusaurus/issues/38 ), copied
below for convenience:
> Hello, may I first confirm that the app.ini PROTOCOL config is case
sensitive (must be lowercase)?
>
> If so, I'd like to suggest for it to be highlighted in the [HTTPS
Setup](https://docs.gitea.com/administration/https-setup#using-the-built-in-server )
page.
> Perhaps something like:
> For the PROTOCOL=https field, make sure https is lowercase. Writing
PROTOCOL=HTTPS may result in a SSL_ERROR_RX_RECORD_TOO_LONG error on
Firefox or ERR_SSL_PROTOCOL_ERROR on Chrome and Edge.
>
> Background
> At first I carelessly wrote PROTOCOL=HTTPS in my app.ini, and Firefox
didn't allow me to connect because:
> Secure Connection Failed
> An error occurred during a connection to gitea.local.lan. SSL received
a record that exceeded the maximum permissible length.
> Error code: SSL_ERROR_RX_RECORD_TOO_LONG
> I spent maybe half an hour troubleshooting my certs, ports, and other
configs before backtracking to the start and realizing the
capitalization difference there 😅 . When I changed that config to
lowercase, it worked.
For this PR I added the note in the Config Cheat Sheet page and fixed
the links to it from the HTTPS Setup page.
Was originally thinking to put the note in the HTTPS Setup page itself,
but since there are 2 sections referencing the PROTOCOL config, I was
thinking it'd be neater and more concise to put it in the Config Cheat
Sheet page instead. Especially since both sections already link to it,
and I actually tried to check that link quite early on in my
troubleshooting (but didn't pay much attention to it since the link was
broken).
## Before/After screenshots as per [this repo's
docs](https://github.com/go-gitea/gitea/tree/main/docs )
Before - links
Note: For this the links weren't broken, the links fix is because they
were broken on gitea.com's docs (see below).
After - links
Before - config cheat sheet
After - config cheat sheet
## Before/After screenshots as per [gitea.com's
docs](https://gitea.com/gitea/gitea-docusaurus )
Before - links
After - links
Before - config cheat sheet
After - config cheat sheet
2023-10-19 16:14:46 +08:00
SandeshPyakurel
776b092863
Typos fixed in documentation files ( #27687 )
...
Typos fixed in multiple docs files.
2023-10-19 02:46:26 -04:00
Sandro Santilli
0f3ea4e1b1
Update agit-support.en-us.md ( #27652 )
...
Clarify Agit PR creation documentation
See https://github.com/go-gitea/gitea/issues/27579
2023-10-17 17:53:36 +08:00
Nanguan Lin
e29e40d128
Change the default branch in the agit docs ( #27621 )
2023-10-14 09:50:23 -04:00
KN4CK3R
c6c829fe3f
Enhanced auth token / remember me ( #27606 )
...
Closes #27455
> The mechanism responsible for long-term authentication (the 'remember
me' cookie) uses a weak construction technique. It will hash the user's
hashed password and the rands value; it will then call the secure cookie
code, which will encrypt the user's name with the computed hash. If one
were able to dump the database, they could extract those two values to
rebuild that cookie and impersonate a user. That vulnerability exists
from the date the dump was obtained until a user changed their password.
>
> To fix this security issue, the cookie could be created and verified
using a different technique such as the one explained at
https://paragonie.com/blog/2015/04/secure-authentication-php-with-long-term-persistence#secure-remember-me-cookies .
The PR removes the now obsolete setting `COOKIE_USERNAME`.
2023-10-14 00:56:41 +00:00
techknowlogick
c573d96b70
rm outdated docs from some languages ( #27530 )
...
related to #27499
2023-10-13 19:29:18 +00:00
Lunny Xiao
dca195e9bd
Fix the robots.txt path
2023-10-11 18:01:52 +08:00
Lunny Xiao
7ff1f2527c
Make actions default enabled for newly created repository if global configuraion enabled ( #27482 )
2023-10-10 14:45:31 +00:00
Nanguan Lin
5b6258a0b9
Fix the wrong HTTP response status code for duplicate packages ( #27480 )
...
fix #27470
(hope there is nothing missing 😢 )
---------
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
2023-10-10 15:39:58 +02:00
Jason Song
2c7b6c378e
Increase queue length ( #27555 )
2023-10-10 18:47:49 +08:00
