I'd like to see what changed in the current build (all the relevant commits), but currently, I can see only the latest commit (HEAD).
Thanks for raising this, Daniel.
Can you give us a bit more information about what you're trying to do with the commits in Pipelines? We have some ideas on this topic (pushes with multiple commits), but would like to understand the problems you're facing first.
We would like to know what changed in all the commits in a push, to optimise what we build for that run of the pipeline.
I think having an environment variable with the commit hash of the previous run is all we'd need -- we could then use Git commands to iterate over the commit range.