forgejo/services/actions
Denys Konovalov 29724f31c5
Refactor commit status for Actions jobs (#23786) (#24060)
Backport #23786

Refactor commit status for Actions jobs (#23786)

Highlights:
- Treat `StatusSkipped` as `CommitStatusSuccess` instead of
`CommitStatusFailure`, so it fixed #23599.
- Use the bot user `gitea-actions` instead of the trigger as the creator
of commit status.
- New format `<run_name> / <job_name> / (<event>)` for the context of
commit status to avoid conflicts.
- Add descriptions for commit status.
- Add the missing calls to `CreateCommitStatus`.
- Refactor `CreateCommitStatus` to make it easier to use.

Co-authored-by: Jason Song <i@wolfogre.com>
2023-04-11 22:37:34 -04:00
..
clear_tasks.go Refactor commit status for Actions jobs (#23786) (#24060) 2023-04-11 22:37:34 -04:00
commit_status.go Refactor commit status for Actions jobs (#23786) (#24060) 2023-04-11 22:37:34 -04:00
init.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
job_emitter.go Refactor commit status for Actions jobs (#23786) (#24060) 2023-04-11 22:37:34 -04:00
job_emitter_test.go Implement actions (#21937) 2023-01-31 09:45:19 +08:00
notifier.go Set ref to fully-formed of the tag when trigger event is release (#23944) (#23989) 2023-04-08 20:43:46 +08:00
notifier_helper.go Refactor commit status for Actions jobs (#23786) (#24060) 2023-04-11 22:37:34 -04:00