community
/
gitea
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
gitea/services/actions
History
Giteabot a9b4aa4cc4
Create commit status when event is `pull_request_sync` (#23683) (#23691) 
Backport #23683 by @sillyguodong

Fix: #23674
If the type of `hook_event` is `pull_request_sync`, also need to insert
a record of `commit_status` into DB.
Because `pull_request` event and `pull_request_sync` event have the same
payload, so the code is reusable.

Screenshot:

![image](https://user-images.githubusercontent.com/33891828/227465436-1b436807-d0b2-4a2b-8890-09d96c7f666d.png)

Co-authored-by: sillyguodong <33891828+sillyguodong@users.noreply.github.com>
 		2023-03-24 17:40:24 -04:00
..
clear_tasks.go Avoid panic caused by broken payload when creating commit status (#23216) (#23294) 2023-03-04 14:23:49 +00:00
commit_status.go Create commit status when event is `pull_request_sync` (#23683) (#23691) 2023-03-24 17:40:24 -04:00
init.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
job_emitter.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
job_emitter_test.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
notifier.go Add context cache as a request level cache (#22294) 2023-02-15 21:37:34 +08:00
notifier_helper.go Avoid panic caused by broken payload when creating commit status (#23216) (#23294) 2023-03-04 14:23:49 +00:00