fix: prevent Not Found error caused by unreachable or stale base SHA#37
Open
melissag-ensemble wants to merge 3 commits into
Open
fix: prevent Not Found error caused by unreachable or stale base SHA#37melissag-ensemble wants to merge 3 commits into
melissag-ensemble wants to merge 3 commits into
Conversation
This reverts commit 62aaf40.
melissag-ensemble
force-pushed
the
ref-not-found-push-deploy
branch
3 times, most recently
from
a87c4d1 to
1b8e0fd
Compare
melissag-ensemble
changed the title
melissag-ensemble
force-pushed
the
ref-not-found-push-deploy
branch
from
1b8e0fd to
977f048
Compare
melissag-ensemble
force-pushed
the
ref-not-found-push-deploy
branch
from
977f048 to
c819f0a
Compare
melissag-ensemble
changed the title
timkim
approved these changes
May 20, 2026
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
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.
Description
Fixes two issues with
tj-actions/changed-files:fetch-depth: 1) couldn't reach the base SHA, causingchanged-filesto fail with "Not Found". Fixed by unshallowing only when a base SHA needs to be reached.workflow_dispatchruns only, so on a push event it used a stale base, diffing a much larger range than necessary and re-deploying unchanged files. Fixed by looking up the latest successful deploy of any trigger.Reverts #36, which masked the crash with
fetch-depth: 0but broke incremental deploys.Ticket
https://jira.corp.adobe.com/browse/DEVSITE-2380
Test