avoid saving secret to .bash_history and showing it on the screen#555
Open
nikelborm wants to merge 1 commit into
Open
avoid saving secret to .bash_history and showing it on the screen#555nikelborm wants to merge 1 commit into
nikelborm wants to merge 1 commit into
Conversation
nikelborm
changed the title
Author
|
UPD. Okay, I looked through the source, and it actually supports reading from stdin already without the need for any bash snippet ( I've updated the PR to show people 2 available ways to set the secret, and the consequences of choosing the way that was shown initially |
nikelborm
force-pushed
the
patch-1
branch
2 times, most recently
from
July 23, 2026 19:12
208325e to
325a7e9
Compare
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
1 participant
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.
Why?
People tend to copy-paste the code from the README