summaryrefslogtreecommitdiff
path: root/vendor/go.etcd.io/bbolt/bolt_unix_aix.go
diff options
context:
space:
mode:
authorChris Evich <cevich@redhat.com>2020-10-05 09:56:15 -0400
committerChris Evich <cevich@redhat.com>2020-10-05 10:13:24 -0400
commit0f04cf27c50a7905a12c3d6741410ba87b3cd7b0 (patch)
tree8fcf95eb117ce71eeb32a9dccd1016e1f07710b0 /vendor/go.etcd.io/bbolt/bolt_unix_aix.go
parent2c9084e2245834094e14e9105e64b6062d70a0f1 (diff)
downloadpodman-0f04cf27c50a7905a12c3d6741410ba87b3cd7b0.tar.gz
podman-0f04cf27c50a7905a12c3d6741410ba87b3cd7b0.tar.bz2
podman-0f04cf27c50a7905a12c3d6741410ba87b3cd7b0.zip
Cirrus: Fix branch-validation failure
When validating code on a branch, determining a starting commit to check from isn't as straightforward as it would seem. Default to using the SHA from last time CI was green. If for some reason that isn't available, use an obviously wrong value to cause an intentional failure. Entirely skip this check on tag-push, since determining a starting point is incredibly difficult to do automatically. Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'vendor/go.etcd.io/bbolt/bolt_unix_aix.go')
0 files changed, 0 insertions, 0 deletions