You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Possible enhancement - give an option to save baseline.json as build artifact?
Implemented pipeline scan with YAML/PowerShell before finding this extension and saved baseline files as build artifacts. I noticed this extension requires git contribute permissions and saves the baseline output to a branch in the repo. Is there a good reason to save to a repo instead of as a build artifact? My concern is that this would cause a little confusion when developers submit PRs and see the modified baseline file added. Original plan was to use the baseline file as a one-time, initial baseline but it seems like this implementation is a bit different since it is updating baseline with each build.
The text was updated successfully, but these errors were encountered:
Possible enhancement - give an option to save baseline.json as build artifact?
Implemented pipeline scan with YAML/PowerShell before finding this extension and saved baseline files as build artifacts. I noticed this extension requires git contribute permissions and saves the baseline output to a branch in the repo. Is there a good reason to save to a repo instead of as a build artifact? My concern is that this would cause a little confusion when developers submit PRs and see the modified baseline file added. Original plan was to use the baseline file as a one-time, initial baseline but it seems like this implementation is a bit different since it is updating baseline with each build.
The text was updated successfully, but these errors were encountered: