gitea/models/actions
Yarden Shoham 6c6a7e7d97
Avoid too long names for actions (#23162) (#23190)
Backport #23162

The name of the job or step comes from the workflow file, while the name
of the runner comes from its registration. If the strings used for these
names are too long, they could cause db issues.

Co-authored-by: Jason Song <i@wolfogre.com>
2023-02-28 13:42:40 +01:00
..
run.go Avoid too long names for actions (#23162) (#23190) 2023-02-28 13:42:40 +01:00
run_job.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
run_job_list.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
run_list.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
runner.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
runner_list.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
runner_token.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
status.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
task.go Avoid too long names for actions (#23162) (#23190) 2023-02-28 13:42:40 +01:00
task_list.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
task_step.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
utils.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
utils_test.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00