silverwind
5e4cd3b577
Remove obsolete actions concurrency notes ( #377 )
...
`concurrency` is fully supported as of v1.26 via https://github.com/go-gitea/gitea/pull/32751 , so remove the unsupported entry and the different-behavior note.
Closes #340
---
This PR was written with the help of Claude Opus 4.6
Reviewed-on: https://gitea.com/gitea/docs/pulls/377
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: silverwind <me@silverwind.io >
Co-committed-by: silverwind <me@silverwind.io >
2026-04-08 23:08:20 +00:00
Excellencedev
0c17ed264d
Add docs for configurable permissions for Actions automatic tokens ( #366 )
...
Docs for https://github.com/go-gitea/gitea/pull/36173
Reviewed-on: https://gitea.com/gitea/docs/pulls/366
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Reviewed-by: silverwind <2021+silverwind@noreply.gitea.com >
Reviewed-by: Nicolas <173651+bircni@noreply.gitea.com >
Co-authored-by: Excellencedev <ademiluyisuccessandexcellence@gmail.com >
Co-committed-by: Excellencedev <ademiluyisuccessandexcellence@gmail.com >
2026-03-24 11:11:25 +00:00
osndok
2b96323137
Note differing default value for concurrency.cancel-in-progress ( #337 )
...
Whereas this bit me pretty hard, and [I don't seem to be the only one](https://forum.gitea.com/t/job-stopping-on-new-push/8142 ), the least we could do is let people know.
---------
Co-authored-by: Robert Hailey <git@osndok.com >
Reviewed-on: https://gitea.com/gitea/docs/pulls/337
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: osndok <osndok@noreply.gitea.com >
Co-committed-by: osndok <osndok@noreply.gitea.com >
2026-02-08 03:08:05 +00:00
dangjinghao
0c7fce4512
Remove run-name section from Comparison to GitHub Actions ( #290 )
...
Since `run-name` support was added in [v1.25.0](https://github.com/go-gitea/gitea/releases/tag/v1.25.0 ), I've removed the outdated `run-name` section from `usage/actions/comparison.md`.
Reviewed-on: https://gitea.com/gitea/docs/pulls/290
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: dangjinghao <dangjinghaoemail@163.com >
Co-committed-by: dangjinghao <dangjinghaoemail@163.com >
2025-11-01 21:11:55 +00:00
Zettat123
a97908040d
Update some docs ( #144 )
...
Close #143
- Add `ORG_PAGING_NUM`
- Remove `hashFiles` from unsupported workflows syntax
Reviewed-on: https://gitea.com/gitea/docs/pulls/144
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com >
Co-authored-by: Zettat123 <zettat123@gmail.com >
Co-committed-by: Zettat123 <zettat123@gmail.com >
2025-01-09 05:27:03 +00:00
jbalonso
ce0d8b898b
Document missing "packages" scope feature for GITEA_TOKEN ( #77 )
...
As per https://github.com/go-gitea/gitea/issues/23642#issuecomment-2119876692 , this documents a missing feature for `GITEA_TOKEN` authorizing access to the package repository.
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
Reviewed-on: https://gitea.com/gitea/docs/pulls/77
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: jbalonso <jbalonso@noreply.gitea.com >
Co-committed-by: jbalonso <jbalonso@noreply.gitea.com >
2024-10-30 22:27:35 +00:00
Lunny Xiao
7a8bc94a8a
Adjust packages and actions articles' sequence on the sidebar
2024-09-02 17:52:58 -07:00
pangliang
9003c4a604
'workflow_dispatch' unsupported description removed ( #54 )
...
For PR: [go-gitea/gitea#28163 ](https://github.com/go-gitea/gitea/pull/28163 )
I saw that there was no description of the use of a single syntax in the original document, so I simply deleted the description that 'workflow_dispatch does not support'
Co-authored-by: pangliang <418094911@qq.com >
Reviewed-on: https://gitea.com/gitea/docs/pulls/54
Reviewed-by: Denys Konovalov <denyskon@noreply.gitea.com >
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com >
Co-authored-by: pangliang <pangliang@noreply.gitea.com >
Co-committed-by: pangliang <pangliang@noreply.gitea.com >
2024-08-19 20:31:59 +00:00
Lunny Xiao
7dc54af200
Remove unnecessary meta data on markdown files ( #12 )
...
Reviewed-on: https://gitea.com/gitea/docs/pulls/12
2024-06-28 19:50:37 +00:00
Lunny Xiao
9a8396aa29
Fix broken links ( #1 )
...
- Always use a relative markdown link so that we can jump even if we edit it in local env or read it in code hosting server.
Reviewed-on: https://gitea.com/gitea/docs/pulls/1
2024-06-14 05:53:15 +00:00
Lunny Xiao
b9e0a85c9b
Use a formal docusaurus i18n structure
2024-06-06 20:44:06 +08:00
