any command with 'secret' doesnt get saved in history, even though no secrets exposed.

ran a command with 'secrets' and found that it doesnt get stored in history.

what idiot or bot thought it would be a good idea to do this stupid shit? it wasnt a problem before. imagine all the people's
time youve wasted bc they're left guessing why the fuck their command isnt in the history, as if they're supposed to just know.

PSReadLine/PSReadLine/History.cs

Line 666 in e266ca6

&& (string.Equals(arg2, "secrets", StringComparison.OrdinalIgnoreCase) || string.Equals(arg2, "secret", StringComparison.OrdinalIgnoreCase));

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues, especially the pinned issues.

Exception report

Screenshot

N/A

Environment data

PS Version: 7.4.13

Steps to reproduce

run echo 'secret' and close the tab and start new and hit up arrow or look at ConsoleHost_history its not there, but not echo 'secre'

Expected behavior

command should be in history. there's no fucking secret in the command, just the string.

Actual behavior

not in history

[dAu6jARL]

I found like this issue.
In PowerShell 7.6.1, any command including case-insensive "token" can't be saved to (Get-PSReadLineOption).HistorySavePath.

[sharpchen]

That's intentional, see:

PSReadLine/PSReadLine/History.cs

Lines 116 to 118 in ac69010

	private static readonly Regex s_sensitivePattern = new Regex(
	"password|asplaintext|token|apikey|secret",
	RegexOptions.Compiled | RegexOptions.IgnoreCase);

I should be able to override with https://learn.microsoft.com/en-us/powershell/module/psreadline/set-psreadlineoption?view=powershell-7.6#example-7-use-historyhandler-to-filter-commands-added-to-history