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

Set fetch depth in deploy job #1822

Merged
merged 2 commits into from
Jan 30, 2024
Merged

Conversation

StevenMaude
Copy link
Contributor

This is an attempt to fix the currently failing "Create Sentry release" step.

This is to attempt to solve failures to create a new Sentry release of
the form:

```
Error: Command failed: /action-release/node_modules/@sentry/cli-linux-x64/bin/sentry-cli releases set-commits 14e3263 --auto
error: Could not find the SHA of the previous release in the git history. If you limit the clone depth, try to increase it. Otherwise, it means that the commit we are looking for was amended or squashed and cannot be retrieved. Use --ignore-missing flag to skip it and create a new release with the default commits count.

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.
```
To help with debugging Sentry related issues in future.

Dependabot will update this for us.
@StevenMaude StevenMaude merged commit a3a9688 into main Jan 30, 2024
6 checks passed
@StevenMaude StevenMaude deleted the steve/set-deploy-fetch-depth branch January 30, 2024 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants