Skip to content

error: No commits found. Change commits range, initial depth or use --ignore-empty to allow empty patch sets #365

Answered by madsh93
madsh93 asked this question in Q&A
Discussion options

You must be logged in to vote

Sorry! This was my own mistake. It seems my Github was not connected to Sentry. This article explains how to fix:

https://charles-stover.medium.com/how-i-debugged-sentry-release-no-commits-found-change-commits-range-d390ba4e326c

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@tatyree
Comment options

@quisido
Comment options

Answer selected by rchl
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
4 participants
Converted from issue

This discussion was converted from issue #362 on November 01, 2021 08:16.