Closed alekseykulikov closed 4 years ago
A lot of time and experiments went to a simple solution for #2 : communicate failed asserts using annotations and attach results to the job.
@denar90 and I think this workflow is close to ideal :) @exterkamp @paulirish let us know what you think.
Thank you @exterkamp for a review πAll the suggestions are in the next
branch and going to be merged to master soon.
Overview for the v2.3.0 release. Please give us your feedback. The tradition of huge rewrites goes on π
Goals:
--uploadUrlMap
to provide compare report automatically, yaml configExpecte workflow: setup action with budgets and temporary storage, get notification when something breaks (example):
Changes:
major
Automatic action annotations for failed assertionsmajor
uploadArtifacts
upload artifacts from the action, instead of extra config, using @actions/artifactupload.*
toserverBaseUrl
andserverToken
with backward compatibility--uploadUrlMap
, but it does not workutils
Notes:
node_modules
folder, it's not possible to review the actual changes. So, I resetnode_modules
from the master but kept all the code changes.