Skip to content
compliance

Add a new section named development in issue view sidebar to interact with branch/pr #24569

Sign in to view logs

Add a new section named development in issue view sidebar to interact with branch/pr

Add a new section named development in issue view sidebar to interact with branch/pr #24569

Triggered via pull request November 29, 2024 05:31
@lunnylunny
synchronize #31899
lunny:lunny/issue_dev
Status Success
Total duration 7m 11s
Artifacts –

pull-compliance.yml

on: pull_request
files-changed  /  detect
4s
files-changed / detect
lint-backend
6m 14s
lint-backend
lint-templates
44s
lint-templates
lint-yaml
0s
lint-yaml
lint-swagger
0s
lint-swagger
lint-spell
24s
lint-spell
lint-go-windows
6m 12s
lint-go-windows
lint-go-gogit
5m 40s
lint-go-gogit
checks-backend
3m 2s
checks-backend
frontend
1m 50s
frontend
backend
6m 50s
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-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-windows
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment