1987c86f3c
Fix URL In Gitea Actions Badge Docs ( #31191 ) ( #31198 )
...
Backport #31191 by @TheBrokenRail
The example URL given in the documentation leads to a 404.
For instance,
`https://your-gitea-instance.com/{owner}/{repo}/actions/workflows/{workflow_file}?branch={branch}&event={event} `
translates to
`https://gitea.thebrokenrail.com/minecraft-pi-reborn/minecraft-pi-reborn/actions/workflows/build.yml `,
which is a 404.
I had to check the [linked GitHub
docs](https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge )
to learn that you have to add `/badge.svg` to the URL.
Example:
https://gitea.thebrokenrail.com/minecraft-pi-reborn/minecraft-pi-reborn/actions/workflows/build.yml/badge.svg
Co-authored-by: TheBrokenRail <17478432+TheBrokenRail@users.noreply.github.com>
2024-05-31 21:08:04 +08:00
42b2541cb5
Update demo site location from try.gitea.io -> demo.gitea.com ( #31054 ) ( #31146 )
...
Backport #31054 by @lunny
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2024-05-29 01:05:07 +00:00
7ecb1d63bb
Move documents under actions ( #31110 ) ( #31116 )
...
Backport #31110 by @lunny
Move secrets and badge under actions
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2024-05-27 23:05:49 +08:00
cc51f70d86
Update Actions documentation missing feature ( #31034 ) ( #31048 )
...
Backport #31034 by @lunny
Fix
https://github.com/go-gitea/gitea/issues/25897#issuecomment-2117145391
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: yp05327 <576951401@qq.com>
2024-05-22 15:04:40 +00:00
70eaa99ac0
fix: change npm scope registry ( #30964 ) ( #30965 )
...
Backport #30964 by @llxlr
https://docs.npmjs.com/cli/v10/using-npm/scope#associating-a-scope-with-a-registry
Co-authored-by: james yang <yanghongday369@gmail.com>
2024-05-13 18:14:31 +02:00
bb7d36d751
Gitea with first upper case + typos ( #30739 ) ( #30747 )
...
Backport #30739 by @mainboarder
* Corrected gitea to Gitea
* fixed some typos
Co-authored-by: mainboarder <git@mainboarder.de>
2024-04-28 23:51:42 +00:00
f3cc00626b
Update actions variables documents ( #30394 )
...
Fix #30393
---------
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: Zettat123 <zettat123@gmail.com>
2024-04-11 11:57:03 +08:00
63c80aeb29
Fix actions design about default actions download url ( #30360 )
...
Fix #30359
2024-04-09 16:39:38 +00:00
c337ff0ec7
Add user blocking ( #29028 )
...
Fixes #17453
This PR adds the abbility to block a user from a personal account or
organization to restrict how the blocked user can interact with the
blocker. The docs explain what's the consequence of blocking a user.
Screenshots:
---------
Co-authored-by: Lauris BH <lauris@nix.lv>
2024-03-04 08:16:03 +00:00
77e29e0c39
Extend issue template yaml engine ( #29274 )
...
Add new option:
`visible`: witch can hide a specific field of the form or the created
content afterwards
It is a string array witch can contain `form` and `content`. If only
`form` is present, it wont show up in the created issue afterwards and
the other way around. By default it sets both except for markdown
As they are optional and github don't have any similar thing, it is non
breaking and also do not conflict with it.
With this you can:
- define "post issue creation" elements like a TODO list to track an
issue state
- make sure to have a checkbox that reminds the user to check for a
thing but dont have it in the created issue afterwards
- define markdown for the created issue (was the downside of using yaml
instead of md in the past)
- ...
## Demo
```yaml
name: New Contribution
description: External Contributor creating a pull
body:
- type: checkboxes
id: extern-todo
visible: [form]
attributes:
label: Contribution Guidelines
options:
- label: I checked there exist no similar feature to be extended
required: true
- label: I did read the CONTRIBUTION.MD
required: true
- type: checkboxes
id: intern-todo
visible: [content]
attributes:
label: Maintainer Check-List
options:
- label: Does this pull follow the KISS principe
- label: Checked if internal bord was notifyed
# ....
```
[Demo
Video](https://cloud.obermui.de/s/tm34fSAbJp9qw9z/download/vid-20240220-152751.mkv )
---
*Sponsored by Kithara Software GmbH*
---------
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>
2024-03-04 01:37:00 +01:00
db545b208b
Implement actions badge svgs ( #28102 )
...
replace #27187
close #23688
The badge has two parts: label(workflow name) and message(action
status). 5 colors are provided with 7 statuses.
Color mapping:
```go
var statusColorMap = map[actions_model.Status]string{
actions_model.StatusSuccess: "#4c1", // Green
actions_model.StatusSkipped: "#dfb317", // Yellow
actions_model.StatusUnknown: "#97ca00", // Light Green
actions_model.StatusFailure: "#e05d44", // Red
actions_model.StatusCancelled: "#fe7d37", // Orange
actions_model.StatusWaiting: "#dfb317", // Yellow
actions_model.StatusRunning: "#dfb317", // Yellow
actions_model.StatusBlocked: "#dfb317", // Yellow
}
```
preview:
---------
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: Giteabot <teabot@gitea.io>
Co-authored-by: delvh <dev.lh@web.de>
2024-02-27 18:56:18 +01:00
6ed74a3fc7
Update docs about `DEFAULT_ACTIONS_URL` ( #29442 )
...
Follow #25581 .
2024-02-27 09:18:35 +00:00
4ba642d07d
Revert "Support SAML authentication ( #25165 )" ( #29358 )
...
This reverts #25165 (5bb8d1924dhttps://github.com/go-gitea/gitea/pull/25165#issuecomment-1960670242
temporary Open #5512 again
2024-02-24 12:18:49 +08:00
5bb8d1924d
Support SAML authentication ( #25165 )
...
Closes https://github.com/go-gitea/gitea/issues/5512
This PR adds basic SAML support
- Adds SAML 2.0 as an auth source
- Adds SAML configuration documentation
- Adds integration test:
- Use bare-bones SAML IdP to test protocol flow and test account is
linked successfully (only runs on Postgres by default)
- Adds documentation for configuring and running SAML integration test
locally
Future PRs:
- Support group mapping
- Support auto-registration (account linking)
Co-Authored-By: @jackHay22
---------
Co-authored-by: jackHay22 <jack@allspice.io>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: Jason Song <i@wolfogre.com>
Co-authored-by: morphelinho <morphelinho@users.noreply.github.com>
Co-authored-by: Zettat123 <zettat123@gmail.com>
Co-authored-by: Yarden Shoham <git@yardenshoham.com>
Co-authored-by: 6543 <6543@obermui.de>
Co-authored-by: silverwind <me@silverwind.io>
2024-02-23 00:08:17 +00:00
3f73eabb66
Explained where create issue/PR template ( #29035 ) ( #29266 )
...
For some user (as me), documentation lack of precision about where to
store issue/pr template.
I propose an enhancement about this point. With bold exergue and
precision about server itself.
I've found some user with same interrogation as :
https://forum.gitea.com/t/issue-template-directory/3328
---------
Co-authored-by: Km <cam.lafit@azerttyu.net>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2024-02-20 14:12:47 -06:00
7430eb9e7f
Update docs for actions variables ( #29239 )
...
the variables is supported, see
a784ed3d6c/docs/content/usage/actions/act-runner.zh-cn.md
2024-02-18 18:04:58 +08:00
f2d5c6edde
Docker Tag Information in Docs ( #29047 )
...
Add more details for the docker tag when using container registry.
---------
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
2024-02-16 21:22:00 +08:00
4635e6d2a6
Runner tokens are multi use ( #29153 )
...
Fixes https://github.com/go-gitea/gitea/issues/28911 .
Co-authored-by: Giteabot <teabot@gitea.io>
2024-02-14 00:24:35 +01:00
470a3e3f89
Update some translations and fix markdown formatting ( #29099 )
...
Update `docs/content/administration/backup-and-restore.zh-cn.md`
`docs/content/contributing/guidelines-frontend.zh-cn.md`
`docs/content/help/support.zh-cn.md`
`docs/content/installation/database-preparation.zh-cn.md`
`docs/content/installation/windows-service.zh-cn.md`
`docs/content/usage/profile-readme.zh-cn.md` to be consistent with the
English document
2024-02-11 19:03:49 +02:00
eb5ddc0a78
Fix incorrect link to swift doc and swift package-registry login command ( #29096 )
...
Fixes a few mistakes in the Swift package registry documentation.
Syntax for the `package-registry login` command can be found
[here](https://github.com/apple/swift-package-manager/blob/main/Documentation/PackageRegistry/PackageRegistryUsage.md#registry-authentication ).
I was not sure the best way to compress all of that information, so I
just focused on making sure the incorrect `package-registry set` command
was fixed.
2024-02-08 08:53:44 +00:00
4bb1fcd2e7
Fix typos in the documentation ( #29048 )
...
Corrected two typos.
2024-02-05 16:19:05 +08:00
a062725758
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
0b1a42ce0f
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
61f8ca4906
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
461d8b53c2
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
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
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
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
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
3d98d99e27
Update actions document about comparsion as Github Actions ( #28560 )
2023-12-20 20:12:25 +00:00
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
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
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
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
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
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
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
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
6ca234a356
Fix wrong relative path on obtain token from command line ( #27850 )
...
Caused by #27845
2023-10-30 23:31:09 -04:00
a18ecaed61
doc: actions/act-runner: document obtaining a runner registration token from gitea CLI ( #27845 )
2023-10-30 19:28:02 -04:00
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
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
e29e40d128
Change the default branch in the agit docs ( #27621 )
2023-10-14 09:50:23 -04:00
c573d96b70
rm outdated docs from some languages ( #27530 )
...
related to #27499
2023-10-13 19:29:18 +00:00
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
04e88e6ca5
Rephrase template documentation to be more clear about .gitea/template ( #27450 )
...
Closes #27336
---------
Co-authored-by: silverwind <me@silverwind.io>
2023-10-06 14:51:33 +08:00
79e1f27eda
Fix incorrect Chinese translation of linked-references.zh-cn.md ( #27382 )
...
---
The original text "To address this" should be translated to "为了解决这个问题".
"工单" looks like corresponds to "issue".
2023-10-02 06:13:08 +00:00
9336286e35
Improve actions docs related to `pull_request` event ( #27126 )
...
Related to #27039
The `ref` property in Gitea Actions is different from GitHub Actions.
This PR improves the documentation to explain the difference.
2023-09-20 06:28:35 +00:00
24a215e317
Remove outdated paragraphs when comparing Gitea Actions to GitHub Actions ( #27119 )
...
No backport needed as this new state only applies to 1.21+
---------
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2023-09-20 11:02:58 +08:00
ed64f1c2b8
Support `.git-blame-ignore-revs` file ( #26395 )
...
Closes #26329
This PR adds the ability to ignore revisions specified in the
`.git-blame-ignore-revs` file in the root of the repository.
The banner is displayed in this case. I intentionally did not add a UI
way to bypass the ignore file (same behaviour as Github) but you can add
`?bypass-blame-ignore=true` to the url manually.
---------
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2023-09-16 17:42:34 +00:00
Giteabot
