Fixing Sentry release, “No commits found. Change commits range…”

When the getsentry/action-release GitHub action fails with “No commits found. Change commits range, initial depth or use — ignore-empty to allow empty patch sets.”

My GitHub deployment workflow, when attempting to upload source maps to Sentry, recently failed with the following unhelpful error.




Staff front end engineer | Tech lead | Architect |

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Manipulating Images using Image Processor in Asp.Net


Linux Performance Analysis

Should developers stick to one Programming Language?

Generasi Gigih Reflection

UI Test Roadmap with Kaspresso

Does Scrum really disempower developers?

Using Git to manage and browse my recipes

5 Awesome RxJS Observables and Operators That Are Often Overlooked

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Charles Stover

Charles Stover

Staff front end engineer | Tech lead | Architect |

More from Medium

Open source, npm, Faker and Chance as an option…

Drawing sectors and pie charts with SVG paths

How to set up SSO authentication and RBAC with Azure AD in a React web app: a simple developer’s…

Want to Compose Maintainable Tests in Your Code? Use Declarative Testing