Skip to content
compliance

Fix the logic of finding the latest pull review commit ID #22845

Sign in to view logs

Fix the logic of finding the latest pull review commit ID

Fix the logic of finding the latest pull review commit ID #22845

Triggered via pull request September 26, 2024 08:19
@Zettat123Zettat123
opened #32139
Zettat123:bugfix/issue-31423
Status Success
Total duration 7m 4s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

pull-compliance.yml

on: pull_request
files-changed  /  detect
5s
files-changed / detect
lint-backend
6m 10s
lint-backend
lint-templates
0s
lint-templates
lint-yaml
0s
lint-yaml
lint-swagger
0s
lint-swagger
lint-spell
29s
lint-spell
lint-go-windows
6m 6s
lint-go-windows
lint-go-gogit
5m 36s
lint-go-gogit
checks-backend
3m 3s
checks-backend
frontend
0s
frontend
backend
6m 39s
backend
docs
0s
docs
actions
0s
actions
Fit to window
Zoom out
Zoom in

Annotations

4 errors
checks-backend
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment
lint-go-gogit
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment
lint-go-windows
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment
lint-backend
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment