Ah, yeah if you don't use the GitHub Actions actor (`GITHUB_ACTOR`) which is available in an Action run, new commits can trigger new builds. - Githubissues

bobheadxi / gobenchdata

📉 Run Go benchmarks, publish results to an interactive web app, and check for performance regressions in your pull requests

https://gobenchdata.bobheadxi.dev

MIT License

142 stars 14 forks source link

Ah, yeah if you don't use the GitHub Actions actor (`GITHUB_ACTOR`) which is available in an Action run, new commits can trigger new builds. #44

Closed Trentonlee closed 3 years ago

Trentonlee commented 3 years ago

Ah, yeah if you don't use the GitHub Actions actor (GITHUB_ACTOR) which is available in an Action run, new commits can trigger new builds.

Unfortunately this can't really be resolved by gobenchdata - you'll have to either:

use the default actor, such that the commit shows author shows up like this (sorry dont have a gobenchdata-relevant example)
push to an alternative branch or repo, like gh-pages

Originally posted by @bobheadxi in https://github.com/bobheadxi/ gobenchdata/issues/43#issuecomment-647562271