getting ressource fails with: fatal: ambiguous argument 'HEAD~1'

concourse / pool-resource

atomically manages the state of the world (e.g. external environments)

Apache License 2.0

54 stars 36 forks source link

getting ressource fails with: fatal: ambiguous argument 'HEAD~1' #55

Closed c0d1ngm0nk3y closed 4 years ago

c0d1ngm0nk3y commented 4 years ago

After updating concourse from 6.2 to 6.3, the pool resource fails on every get with

fatal: ambiguous argument 'HEAD~1': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
basename: missing operand
Try 'basename --help' for more information

This problem was introduced with the docker image concourse/pool-resource:1.1.2. Using concourse/pool-resource:1.1.1 instead works fine.

c0d1ngm0nk3y commented 4 years ago

Looks like a untested git version to me :(

tlwr commented 4 years ago