How to use file commit SHAs with API to ensure content isn't overwritten

ferahl

Hi, looking at the docs to commit files:

https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Busername%7D/%7Brepo_slug%7D/src#post

It's unclear to me how the last known commit SHA for a file could be passed in so that the commit throws a conflict if there have been subsequent modifications. I can't imagine the API would be very useful without that so wondering what I'm missing!?

Thanks