Repository navigation
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
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.
Fixes #74
Summary
Emits an explicit
@actions/corewarning whenskip-ssh-setupisfalse(default) andprivate-keyis empty (for example, when${{ secrets.PRIVATE_KEY }}evaluates to an empty string due to a secret name typo or missing repository/environment secret, as reported in #74):ssh()startedssh-agent($ ssh-agent -a /tmp/ssh-auth.sock), exportedSSH_AUTH_SOCK, and silently skippedssh-add -whenprivate-keywas empty, leaving users puzzled by downstreamPermission denied (publickey,password)errors.No "private-key" input provided (or the referenced GitHub Actions secret is empty). Proceeding without adding an SSH key to ssh-agent.) so misconfigured secret names are immediately obvious in the workflow run log.