Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Gracefully handle errors for repositories without any previous commits #365

Closed
3 tasks done
jackton1 opened this issue Feb 14, 2022 · 2 comments · Fixed by #404
Closed
3 tasks done

[BUG] Gracefully handle errors for repositories without any previous commits #365

jackton1 opened this issue Feb 14, 2022 · 2 comments · Fixed by #404
Labels
bug Something isn't working

Comments

@jackton1
Copy link
Member

jackton1 commented Feb 14, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Does this issue exist in the latest version?

  • I'm using the latest release

Describe the bug?

https://github.com/tj-actions/glob2/runs/5186771164?check_suite_focus=true

To Reproduce

https://github.com/tj-actions/glob2/runs/5186771164?check_suite_focus=true

What OS are you seeing the problem on?

all

Expected behavior?

Skipped change detection

Using git rev-list --count HEAD

https://stackoverflow.com/a/15225530/4584672

Relevant log output

No response

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jackton1 jackton1 added the bug Something isn't working label Feb 14, 2022
@github-actions
Copy link
Contributor

Thanks for reporting this issue, don't forget to star this project to help us reach a wider audience.

@jackton1
Copy link
Member Author

jackton1 added a commit that referenced this issue Feb 26, 2022
…ry (#404)

* fix: Handle errors for repositories without any previous commit history

Fixes: #365

* Update diff-sha.sh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant