Closed vorburger closed 11 months ago
Is this possibly caused by https://github.com/rossjrw/pr-preview-action/commit/aa0f798d7a8862266c793affdfd62ad96edd14d9 & Co?
Why does your action have fancy code to find its own revision? That's curious / interesting - doesn't GitHub check-out the actions?
Or is this not failing to clone the action, but the repo? The "source" or the "target" deploy-repository
one?
Apparently the change I made in https://github.com/www-learn-study/saraswati.learn.study/commit/8e058c4460c6582eea099af5e287c0bfac275018 was the culprit causing this?!
Reverting that in https://github.com/www-learn-study/saraswati.learn.study/pull/55 seems to do the trick (but makes https://github.com/www-learn-study/saraswati.learn.study/issues/50 re-appear, but that's another story).
That using a verion tag instead of a SHA fixes this seems really weird, to me... no action should prevent me from using a SHA (which is considered more secure) instead of a Tag!
Why does your action have fancy code to find its own revision? That's curious / interesting - doesn't GitHub check-out the actions?
It's to display the specific action version in the message with the preview link. E.g. if you use rossjrw/pr-preview-action@v1
, I feel that it's more useful for the message to show 'v1.2.1' or whatever instead of just 'v1'.
no action should prevent me from using a SHA (which is considered more secure) instead of a Tag!
You're right, and in fact, this was already fixed in https://github.com/rossjrw/pr-preview-action/pull/36. But since then, I've managed to accidentally remove that fallback in https://github.com/rossjrw/pr-preview-action/commit/aa0f798d7a8862266c793affdfd62ad96edd14d9. This one's on me.
In https://github.com/www-learn-study/saraswati.learn.study/actions/runs/6729181929/job/18289629833?pr=20 I ran into this: