5 Commits

Author	SHA1	Message	Date
silverwind	a0160694b9	Enable nilnil linter for new code (#36591) ... Fixes: https://github.com/go-gitea/gitea/issues/36152 Enable the `nilnil` linter while adding `//nolint` comments to existing violations. This will ensure no new issues enter the code base while we can fix existing issues gradually. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>	2026-02-16 09:57:18 +00:00
Lunny Xiao	06ccda06c4	Fix possible panic (#34508)	2025-05-22 12:59:42 +00:00
badhezi	0534eddd16	Use run-name and evaluate workflow variables (#34301) ... This addresses https://github.com/go-gitea/gitea/issues/34247 depends on https://gitea.com/gitea/act/pulls/137 I couldn't find any previous implementation for `run-name` support on workflows so I created one. Key points: All dispatched workflows, scheduled workflows and detected workflows (from different hooks) will use and evaluate `run-name` if exists, with the corresponding gitea context and variables. This will be used as the Action run title and replace the default commit message being used today. Had to change act package jobparser (see link above) and create two helpers 3a1320c70d/models/actions/utils.go (L86) and 3a1320c70d/services/actions/context.go (L169) to pass the correct types to [GenerateGiteaContext](https://github.com/go-gitea/gitea/pull/34301/files#diff-9c9c27cb61a33e55ad33dc2c2e6a3521957a3e5cc50ddf652fdcd1def87b044dR86) and [WithGitContext](65c232c4a5/pkg/jobparser/jobparser.go (L84)) respectively. <img width="1336" alt="Screenshot 2025-04-28 at 17 13 01" src="https://github.com/user-attachments/assets/73cb03d0-23a0-4858-a466-bbf0748cea98" />	2025-05-20 02:24:10 +00:00
TheFox0x7	ee3c82f874	Enable addtional linters (#34085) ... enable mirror, usestdlibbars and perfsprint part of: https://github.com/go-gitea/gitea/issues/34083 --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>	2025-04-01 10:14:01 +00:00
Zettat123	d0962ce3da	Move some Actions related functions from routers to services (#33280) ... Move the main logic of `generateTaskContext` and `findTaskNeeds` to the `services` layer. This is a part of #32751, since we need the git context and `needs` to parse the concurrency expressions. --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>	2025-01-15 21:34:30 +08:00