chore: fail fast on cron generate step #2533
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@rakellkizz is attempting to deploy a commit to the DeepSource Team on Vercel. A member of the Team first needs to authorize it. |
Author
|
This PR is related to the existing issue reporting the cron failure due to Related issue: #<#2532> |
|
This is solved by regenerating and correctly wiring a classic PAT. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change makes the cron workflow fail fast during the
make generatestepby using
set -e.It does not change behavior or output, but avoids false-success runs and makes
authentication failures (401 Bad credentials) clearly visible in GitHub Actions logs.