Add GitHub Actions summary for the create evidence command #112
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jul 27, 2025
mnsboev
force-pushed
the
create-evidence-summary
branch
from
ef70f1c to
99f5794
Compare
selalererjfrog
approved these changes
Jul 27, 2025
mnsboev
force-pushed
the
create-evidence-summary
branch
from
7fd425b to
2c3acf1
Compare
dortam888
reviewed
Aug 4, 2025
| "regexp" | ||
| "strings" | ||
|
|
||
| clientLog "github.com/jfrog/jfrog-client-go/utils/log" |
Collaborator
There was a problem hiding this comment.
why is it different than other places in the code?
| CreatedAt string `json:"created_at"` | ||
| CreatedBy string `json:"created_by"` | ||
| Verified bool `json:"verified"` | ||
| ProviderId string `json:"provider_id"` |
Collaborator
There was a problem hiding this comment.
Note to self, don't forget to add stage
| SubjectType: commandsummary.SubjectTypeReleaseBundle, | ||
| ReleaseBundleName: c.releaseBundle, | ||
| ReleaseBundleVersion: c.releaseBundleVersion, | ||
| RepoKey: utils.BuildReleaseBundleRepoKey(c.project), |
Collaborator
There was a problem hiding this comment.
Are those needed: CreatedAt? CreatedBy? ProviderId?
| Verified: response.Verified, | ||
| DisplayName: displayName, | ||
| SubjectType: commandsummary.SubjectTypePackage, | ||
| RepoKey: c.packageService.GetPackageRepoName(), |
Collaborator
There was a problem hiding this comment.
CreatedAt? CreatedBy? ProviderId?
|
|
||
| func (c *createEvidenceCustom) recordSummary(response *model.CreateResponse) { | ||
| commandSummary := commandsummary.EvidenceSummaryData{ | ||
| Subject: c.subjectRepoPath, |
Collaborator
There was a problem hiding this comment.
RepoKey? CreatedAt? CreatedBy? ProviderId?
| BuildName: c.buildName, | ||
| BuildNumber: c.buildNumber, | ||
| BuildTimestamp: timestamp, | ||
| RepoKey: utils.BuildBuildInfoRepoKey(c.project), |
Collaborator
There was a problem hiding this comment.
CreatedBy? CreatedAt? ProviderId?
mnsboev
force-pushed
the
create-evidence-summary
branch
from
7fbbd16 to
8f52f88
Compare
naveenku-jfrog
pushed a commit
to naveenku-jfrog/jfrog-cli-artifactory
that referenced
this pull request
Aug 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add evidence summary section for Create Evidence Command
This PR is part of a series of three that enhances the documentation for the "create evidence" command by introducing a summary markdown table.
jfrog-cli-core PR: jfrog/jfrog-cli-core#1423
jfrog-cli PR: jfrog/jfrog-cli#3042
Summary
This addition aims to improve the user experience by providing a clear and concise overview of the evidence being created. The markdown table includes the following columns:
Evidence Subject: Links to the relevant evidence files, allowing users to easily access them.
Evidence Type: Specifies the type of evidence being recorded (e.g., in-toto).
Verification Status: Indicates whether the evidence has been verified, complete with visual status indicators (e.g., ✅ Verified).
Example Output
When the create evidence command is executed, users will see a collapsible section that looks like this:
🔎 Evidence