silverwind and GitHub
d953a4b3b6
Update JS and PY dependencies, build for es2020 browsers ( #28977 )
...
- Update all JS dependencies minus @mcaptcha/vanilla-glue
- Fix new lint errors
- Regenerate SVGs
- Switch to maintained stylelint stylistic plugin
- Tested Mermaid, Citation, Swagger, sorting
- Raise ESBuild target to `es2020` as dictated by `pretty-ms`
dependency.
2024-02-02 09:36:32 +00:00
b244ceebfa
Add htmx guidelines ( #28993 )
...
To make sure we don't abuse it.
---------
Signed-off-by: Yarden Shoham <git@yardenshoham.com >
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com >
Co-authored-by: delvh <dev.lh@web.de >
2024-01-31 23:36:23 +01:00
yp05327 and GitHub
b56c07f278
Fix doc img path in profile readme ( #28994 )
...
https://gitea.com/gitea/gitea-docusaurus/actions/runs/1007/jobs/0#jobstep-9-25
2024-01-31 21:32:17 +08:00
Mike Cifelli and GitHub
0eccee4491
Update golang links to use https ( #28980 )
...
Many of the golang links point to the old site and don't use https. This
pull request updates these outdated links to https://go.dev .
https://github.com/go-gitea/gitea/issues/28979
2024-01-30 03:11:11 +02:00
wackbyte and GitHub
cf068ddcf6
Fix inconsistent naming of OAuth 2.0 ENABLE setting ( #28951 )
...
Renames it to `ENABLED` to be consistent with other settings and
deprecates it.
I believe this change is necessary because other setting groups such as
`attachment`, `cors`, `mailer`, etc. have an `ENABLED` setting, but
`oauth2` is the only one with an `ENABLE` setting, which could cause
confusion for users.
This is no longer a breaking change because `ENABLE` has been set as
deprecated and as an alias to `ENABLED`.
2024-01-28 12:36:44 +00:00
6543 and GitHub
569ccbfc9e
Add screenshot for "Profile Readmes" to docs ( #28964 )
...
introduced in #23260 ... the docs still looks to empty:
https://docs.gitea.com/usage/profile-readme
this changes it :)
2024-01-28 00:20:17 +01:00
Mechiel Lukkien and GitHub
f15ae98cad
In administration documentation about environment variables, point to those for the Go runtime instead of Go compiler ( #28859 )
...
The previous variables are used by the compiler and aren't too useful
for non-developers. The newly listed variables are more likely to be of
interest.
Apologies for this drive-by PR, I probably missed instructions from the
contributors guide. The patch can be regarded as a simple way to explain
the problem and solution. Feel free to close and possibly create a new
PR that does adhere to the contributors guide.
2024-01-20 10:12:20 +08:00
KN4CK3R and GitHub
2e821366c4
Fix some RPM registry flaws ( #28782 )
...
Related #26984
(https://github.com/go-gitea/gitea/pull/26984#issuecomment-1889588912 )
Fix admin cleanup message.
Fix models `Get` not respecting default values.
Rebuild RPM repository files after cleanup.
Do not add RPM group to package version name.
Force stable sorting of Alpine/Debian/RPM repository data.
Fix missing deferred `Close`.
Add tests for multiple RPM groups.
Removed non-cached `ReplaceAllStringRegex`.
If there are multiple groups available, it's stated in the package
installation screen:
2024-01-19 11:37:10 +00:00
b5e93334ca
Retarget depending pulls when the parent branch is deleted ( #28686 )
...
Sometimes you need to work on a feature which depends on another (unmerged) feature.
In this case, you may create a PR based on that feature instead of the main branch.
Currently, such PRs will be closed without the possibility to reopen in case the parent feature is merged and its branch is deleted.
Automatic target branch change make life a lot easier in such cases.
Github and Bitbucket behave in such way.
Example:
$PR_1$: main <- feature1
$PR_2$: feature1 <- feature2
Currently, merging $PR_1$ and deleting its branch leads to $PR_2$ being closed without the possibility to reopen.
This is both annoying and loses the review history when you open a new PR.
With this change, $PR_2$ will change its target branch to main ($PR_2$: main <- feature2) after $PR_1$ has been merged and its branch has been deleted.
This behavior is enabled by default but can be disabled.
For security reasons, this target branch change will not be executed when merging PRs targeting another repo.
Fixes #27062
Fixes #18408
---------
Co-authored-by: Denys Konovalov <kontakt@denyskon.de >
Co-authored-by: delvh <dev.lh@web.de >
2024-01-17 01:44:56 +01:00
crapStone and GitHub
b00382e80c
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 and GitHub
b932680971
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 and GitHub
7f54d4fbab
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 and GitHub
6cd0f343a3
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 and GitHub
edc7cb0b70
Normalize oauth email username ( #28561 )
2024-01-03 18:48:20 -06:00
9384b5b310
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 and GitHub
de80cd459c
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 and GitHub
225ad199d0
Improve document for ARTIFACT_RETENTION_DAYS ( #28646 )
...
Follow #28626
2023-12-29 06:44:58 +00:00
wxiaoguang and GitHub
902b9ca494
Improve 1.22 document for Database Preparation ( #28643 )
...
Fix #28247
2023-12-29 05:42:22 +00:00
Denys Konovalov and GitHub
a60b120f41
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 and GitHub
c3f5a58544
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 and GitHub
b1315df808
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 and GitHub
c6a236148d
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 and GitHub
831a1c2276
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 and GitHub
57837301fe
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 and GitHub
54f64c130b
Update actions document about comparsion as Github Actions ( #28560 )
2023-12-20 20:12:25 +00:00
Lunny Xiao and GitHub
272f1b805c
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 and GitHub
9e9038ed05
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 and GitHub
0e97abdfd5
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 and GitHub
4e05e9d5dd
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 and GitHub
6db46ff17a
Fix Chinese translation of config cheat sheet[API] ( #28472 )
2023-12-15 00:00:04 +08:00
wxiaoguang and GitHub
4d10baf111
Fix documents for "custom/public/assets/" ( #28465 )
...
Fix #28463
2023-12-14 08:52:16 +00:00
David Hulick and GitHub
eaaa3369f8
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 and GitHub
a6457ac930
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 and GitHub
e530d8eef1
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 and GitHub
2233876d46
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 and GitHub
aaa49886ff
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 and GitHub
5195cc7e92
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 and GitHub
6d8e32689d
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 and GitHub
697a90b01c
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 and GitHub
c333830929
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
f6948ba8ee
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 and GitHub
8025369dd8
Allow to set explore page default sort ( #27951 )
...
as title
---
*Sponsored by Kithara Software GmbH*
2023-11-09 10:11:45 +00:00
6543 and GitHub
7ac34b57d4
Document REACTION_MAX_USER_NUM setting option ( #27954 )
...
https://github.com/go-gitea/gitea/blob/4a0103fa293cc42075d4a9c10ca4dffa9c2d3a40/modules/setting/ui.go#L24
https://github.com/go-gitea/gitea/blob/4a0103fa293cc42075d4a9c10ca4dffa9c2d3a40/modules/setting/ui.go#L77
---
*Sponsored by Kithara Software GmbH*
2023-11-08 01:50:31 +01:00
Nanguan Lin and GitHub
68a216fd3f
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](https://github.com/docker/build-push-action/commit/d8823bfaed2a82c6f5d4799a2f8e86173c461aba )
as the Gitea Actions Doc mentioned too.
2023-11-06 22:45:37 +08:00
Moritz Poldrack and GitHub
c9b2b9c245
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 and GitHub
e5c0884503
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 and GitHub
494d46b23f
Fix wrong relative path on obtain token from command line ( #27850 )
...
Caused by #27845
2023-10-30 23:31:09 -04:00
nodiscc and GitHub
810777a961
doc: actions/act-runner: document obtaining a runner registration token from gitea CLI ( #27845 )
2023-10-30 19:28:02 -04:00
HoshinoRei and GitHub
0256f70d27
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 and GitHub
91ee9fedea
[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
