Use base SHA instead of base branch since the base branch #2
+17
−4
Conversation
This file contains 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
jainankit
changed the title
draftcode
reviewed
Dec 7, 2023
| @@ -16,12 +16,22 @@ jobs: | |||
| node-version: '18' | |||
There was a problem hiding this comment.
Cannot comment on the exact line, but on line 13, add
with:
filter: 'blob:none'
depth: 0
draftcode
approved these changes
Dec 7, 2023
|
Skipping bot pull request creation because the queue is empty and this pull request is up to date with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A PR could be using a stale base SHA. When calculating the affected targets, we should use the diff from base SHA to the head SHA. Since GH does not provide base SHA directly in the workflow action, make an API call to get the results.