The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
How to use file commit SHAs with API to ensure content isn't overwritten
ferahl
January 30, 2019 edited
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
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Copyright © 2026 Atlassian