# BUILDKITE\_COMMIT (cannot) be resolved to a ref

**URL:** <https://forum.buildkite.community/t/buildkite-commit-cannot-be-resolved-to-a-ref/510>\
**Category:** Features Requests\
**Created:** [May 22, 2019, 9:17pm UTC](https://forum.buildkite.community/t/buildkite-commit-cannot-be-resolved-to-a-ref/510 "2019-05-22T21:17:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![haraldschioberg](https://avatars.discourse-cdn.com/v4/letter/h/f1d935/32.png) [@haraldschioberg](https://forum.buildkite.community/u/haraldschioberg)\
**Post date:** [May 22, 2019, 9:17pm UTC](https://forum.buildkite.community/t/buildkite-commit-cannot-be-resolved-to-a-ref/510/1 "2019-05-22T21:17:03Z")

</div>

when running e.g. from a scheduled job the BUILDKITE\_COMMIT may be “HEAD”. On a busy repo this means that each step of the pipeline will most likely run against a different git ref…

There is no real mechanism for pinning the BUILDKITE\_COMMIT in this scenario