Zoran Regvart
Zoran Regvart
The current implementation doesn't look as appealing to me, I think the (almost) default decoration for links looks better.
### Feature request I'm mostly interested in having the `experimental.tekton.dev/execution-mode` annotation available in the SLSA provenance. It might be useful to place all TaskRun annotations in there as well. A...
## Short description `opa fmt` will reformat this Rego ([playground](https://play.openpolicyagent.org/p/O4TLbhivHd)): ```rego package play x := "\u0000" ``` as ```rego package play x := "\x00" ``` Which causes `rego_parse_error: illegal escape...
#### Summary Fixes #5977 The prompt for selecting the site to work with in a project with multiple workspaces breaks CI workflows that are non-interactive. The proposed solution in providing...
**What this PR does / why we need it**: Updates from `oras.land/oras-go` to `oras.land/oras-go/v2`. The main user facing change is that the `--plain-http` parameter is now required even when accessing...
Hello :wave: Are Rego rules without the `msg`, e.g. ones returning a boolean supported? Given this Rego rule: ```rego package example violation[msg] { msg := "should emit violation" } violation[msg]...
### Feature request The SLSA v1 specification [allows `"git*"`](https://github.com/in-toto/attestation/blob/main/spec/v1/digest_set.md#gitcommit-gittree-gitblob-gittag) as algorithm value for `predicate.buildDefinition.resolvedDependencies.digest`. Currently [it is set](https://github.com/tektoncd/chains/blob/main/pkg/chains/formats/slsa/internal/material/material.go) to `"sha1"` and the value is the git commit id. With `artifacts.pipelinerun.format=slsa/v2alpha2`...
Currently Docker image references with tag and digest are [not supported](https://github.com/containers/image/blob/d372f0e440d35c6041de39023b0b6eb131fba54b/docker/docker_transport.go#L79-L81). This leads to failure when trying to invoke tools that depend on `containers/image`, like `skopeo`: ``` $ skopeo inspect...
Adds the `--` separator parameter so delve doesn't try to parse any command line parameters intended for the target binary.
If a Check suite is marked as required on GitHub it must report successful result. Currently there is no option to mark the Check suite as skipped (see https://github.com/orgs/community/discussions/13690). Perhaps...