-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(#7): add output to gha for retrieving measured data for total and for every lap as json #15
feat(#7): add output to gha for retrieving measured data for total and for every lap as json #15
Conversation
…repository' attribute
…riting into GITHUB_OUTPUT
…ngle quotes because compared json contains double quotes itself
…ent available for laps, too
… that the lap measures are made available via output
…urrently the laps contain wrong label but the run succeeds
…olean string result to numeric and compare it
@rajbos, it took me a while but now we have an example workflow which demonstrates usage of the different outputs (either provided by In general, the output of the measurements had to be stored non-pretty-printed due to github action restrictions of multiline strings. Storing the json string in a 1-liner seemed way easier for me. This implies that the consumer of the output data needs to pretty print the json string. Can you please re-review? |
… add section describing data consumption
The measured data is made available as json string via step output as follows:
display-results
task before:${{ steps.XYZ.outputs.data-total-json }}
get-measurement
task before:${{ steps.XYZ.outputs.data-lap-json }}