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.”
3 min readSep 2, 2021
My GitHub deployment workflow, when attempting to upload source maps to Sentry, recently failed with the following unhelpful error.
Error: Command failed: /action-release/dist/sentry-cli releases set-commits *** --auto
error: No commits found. Change commits range, initial depth or use --ignore-empty to allow empty patch sets.Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
Please attach the full debug log to all bug reports.
One would think GitHub could identify the commits range in the workflow, so why is it failing to find them? The suggestion to unblock this issue with --ignore-empty is bad advice, as the change set should not be empty in the first place. To resolve this, I followed the subsequent instructions and set my SENTRY_LOG_LEVEL environment variable to debug.
Once debug logs were enabled, I found that Sentry’s GitHub action was using the git history for a different repository altogether. I searched my repository…
