Skip to content

Commit

Permalink
weird I thought I did this yesterday
Browse files Browse the repository at this point in the history
Signed-off-by: chaosinthecrd <tom@tmlabs.co.uk>
  • Loading branch information
ChaosInTheCRD committed May 10, 2024
1 parent 55917ef commit ce45f1f
Showing 1 changed file with 1 addition and 14 deletions.
15 changes: 1 addition & 14 deletions docgen/docs.go
Original file line number Diff line number Diff line change
Expand Up @@ -27,20 +27,7 @@ import (
"github.com/spf13/cobra/doc"

"github.com/in-toto/go-witness/attestation"

Check failure on line 29 in docgen/docs.go

View workflow job for this annotation

GitHub Actions / Verify Docgen

github.com/in-toto/go-witness@v0.3.1: replacement directory ../go-witness does not exist
// this feels like an annoying way of importing them as it will need edited for each attestor added
_ "github.com/in-toto/go-witness/attestation/aws-iid"
_ "github.com/in-toto/go-witness/attestation/commandrun"
_ "github.com/in-toto/go-witness/attestation/environment"
_ "github.com/in-toto/go-witness/attestation/gcp-iit"
_ "github.com/in-toto/go-witness/attestation/git"
_ "github.com/in-toto/go-witness/attestation/github"
_ "github.com/in-toto/go-witness/attestation/gitlab"
_ "github.com/in-toto/go-witness/attestation/jwt"
_ "github.com/in-toto/go-witness/attestation/material"
_ "github.com/in-toto/go-witness/attestation/maven"
_ "github.com/in-toto/go-witness/attestation/oci"
_ "github.com/in-toto/go-witness/attestation/product"
_ "github.com/in-toto/go-witness/attestation/sarif"
_ "github.com/in-toto/witness"

Check failure on line 30 in docgen/docs.go

View workflow job for this annotation

GitHub Actions / lint

import "github.com/in-toto/witness" is a program, not an importable package (typecheck)

Check failure on line 30 in docgen/docs.go

View workflow job for this annotation

GitHub Actions / fmt / witness

import "github.com/in-toto/witness" is a program, not an importable package
)

var directory string
Expand Down

0 comments on commit ce45f1f

Please sign in to comment.