# PkgBenchmark.jl workflow

**URL:** <https://discourse.julialang.org/t/pkgbenchmark-jl-workflow/24472>\
**Category:** General Usage\
**Tags:** benchmark, benchmarktools\
**Created:** [May 22, 2019, 11:58am UTC](https://discourse.julialang.org/t/pkgbenchmark-jl-workflow/24472 "2019-05-22T11:58:59Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)\
**Post date:** [August 19, 2019, 8:45pm UTC](https://discourse.julialang.org/t/pkgbenchmark-jl-workflow/24472/3 "2019-08-19T20:45:33Z")

</div>

(Continuing the discussion in [How to run benchmark CI on every commit? - #3 by tkf](https://discourse.julialang.org/t/how-to-run-benchmark-ci-on-every-commit/27034/3))

FYI I just set up CI to run `PkgBenchmark.judge` [https://github.com/tkf/Transducers.jl/pull/32](https://github.com/tkf/Transducers.jl/pull/32) and I find it pretty useful. Feel free to grab some helper script/setting from there. There were some bits that were not super obvious (like how to invoke `git fetch` to pull the `master` branch so that `PkgBenchmark` can switch to it.).

---

_[View the full topic](https://discourse.julialang.org/t/pkgbenchmark-jl-workflow/24472)._