Earl Warren 387aea4434 fix(actions): the trigger user of a schedule is the action user ... The user that caused the notification to re-evaluates the schedules is not the one that will trigger the workflows. They are background tasks that are authored by the action user (id -2). Such a mis-assignment is problematic when the user that caused the notification is deleted. Fixes: https://codeberg.org/forgejo/forgejo/issues/3211 (cherry picked from commit c3e2c25359)		2024-04-14 17:36:42 +00:00
..
cleanup.go	Artifacts retention and auto clean up (#26131)	2023-09-06 07:41:06 +00:00
clear_tasks.go	Make Actions tasks/jobs timeouts configurable by the user (#27400) (#27402)	2023-10-03 10:26:35 +08:00
commit_status.go	Fix pull request check list is limited (#26179)	2023-07-31 02:21:09 +00:00
init.go	Move notification interface to services layer (#26915)	2023-09-05 18:37:47 +00:00
job_emitter.go	The job should always run when `if` is `always()` (#29464) (#29469)	2024-03-10 18:08:15 +07:00
job_emitter_test.go	The job should always run when `if` is `always()` (#29464) (#29469)	2024-03-10 18:08:15 +07:00
main_test.go	[ACTIONS] skip superflous pull request synchronized event (#2314)	2024-02-13 12:00:27 +01:00
notifier.go	Fix invalid link of the commit status when ref is tag (#29752) (#29908)	2024-03-21 17:09:50 +01:00
notifier_helper.go	fix(actions): the trigger user of a schedule is the action user	2024-04-14 17:36:42 +00:00
notifier_helper_test.go	[ACTIONS] skip superflous pull request synchronized event (#2314)	2024-02-13 12:00:27 +01:00
schedule_tasks.go	[ACTIONS] on.schedule: the event is always "schedule"	2023-12-23 15:58:37 +01:00