Skip to content

feat: support start time parameter on read changes #1505

feat: support start time parameter on read changes

feat: support start time parameter on read changes #1505

Triggered via pull request January 31, 2025 13:53
Status Failure
Total duration 4m 58s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

main.yaml

on: pull_request
goreleaser
0s
goreleaser
binary-provenance  /  detect-env
binary-provenance / detect-env
image-provenance  /  detect-env
image-provenance / detect-env
binary-provenance  /  generator
binary-provenance / generator
image-provenance  /  generator
image-provenance / generator
binary-provenance  /  upload-assets
binary-provenance / upload-assets
image-provenance  /  final
image-provenance / final
binary-provenance  /  final
binary-provenance / final
verification-with-cosign
0s
verification-with-cosign
verification-with-slsa-verifier
0s
verification-with-slsa-verifier
Fit to window
Zoom out
Zoom in

Annotations

8 errors
Lints: cmd/tuple/changes_test.go#L144
cannot use "2022-01-01T00:00:00Z" (untyped string constant) as time.Time value in struct literal
Lints: cmd/tuple/changes_test.go#L238
cannot use "2022-01-01T00:00:00Z" (untyped string constant) as time.Time value in struct literal
Lints: cmd/tuple/changes_test.go#L310
cannot use "2022-01-01T00:00:00Z" (untyped string constant) as time.Time value in struct literal (typecheck)
Lints
issues found
Tests: cmd/tuple/changes_test.go#L144
cannot use "2022-01-01T00:00:00Z" (untyped string constant) as time.Time value in struct literal
Tests: cmd/tuple/changes_test.go#L238
cannot use "2022-01-01T00:00:00Z" (untyped string constant) as time.Time value in struct literal
Tests: cmd/tuple/changes_test.go#L310
cannot use "2022-01-01T00:00:00Z" (untyped string constant) as time.Time value in struct literal
Tests
Process completed with exit code 2.