Lachlan Donald

I've avoided this because historically (pre git 1.9) shallow clones had lots of edge conditions. Perhaps we will look at this post v3.

Apologies, I believe this is a regression caused by https://github.com/buildkite/agent/pull/908. It should work as you described, although I deeply regret making it work like that in the first place!

> The way we're using it seems undocumented. If you do choose to fix it, can we document it? Yup, absolutely will do, as well as add a test to...

Updated to remove the experiment @moskyb

I'm no longer Buildkite staff @leakingtapan! Just a contributor like yourself.

> Given that this behaviour is intended to be helpful, and in many cases is likely being used as intended, it might be best to simply disallow this behaviour for...

My take on this is that it's dangerous behaviour. Rsync uses a trailing slash on destinations to get the different behaviour, I reckon we should do the same: `buildkite-agent artifact...

Yup, I agree this would be a nice addition.

This would be really nice to have, it's fairly surprising it doesn't work to users. If I was to add a PR that added whether the artifact was executable in...

Actually, I take it back, it would need to be returned from the artifact search.