Closed xThaid closed 5 months ago
I removed benchmark
label as it will trigger the job that issues a comment in this PR, which will fail due to lack of permissions. I believe that putting this modified workflow on the master branch should solve permission issues.
The motivation is that performance changes should be visible by default (as opposed to manually triggering the benchmarks).
benchmark
label, benchmarks are run and compared to the base branch as the baseline.Github job summary
, so one doesn't have to search through logs.I am not adding
benchmark
label, as the job will fail. Most likely we need to merge this first, so permissions are propagated correctly. Here is the preview: https://github.com/xThaid/coreblocks/pull/2#issuecomment-2054193764Fixes #657.