Fred Eisele

On Windows there seems to be an unresolved dependency on https://github.com/CDSoft/pp Is this appropriate?

Take a look at my comment in #747

The approaches mentioned above may be useful in correcting the documentation found here. https://mikefarah.gitbook.io/yq/usage/tips-and-tricks#quotes-in-windows-powershell

I did not write it to be a complete wrapper (the eval command is assumed) but other than that it is pretty much what you might expect. e.g. ```powershell yq.ps1...

I got most of it working and then took a holiday. I have to get some things done for my day job and then I will get back to this....

The work around is to quote in the following way. ```powershell .\yq.exe e '{\"wrap\": .}' sample.yaml ``` You can see that this is strictly a Powershell issue by the following...

Here is a `yq.ps1` that seems to do the necessary escaping. ```powershell Param( [string]$command, [string]$yamlFile ) $escCommand = $command -replace '"','\"' -replace ' ','' $evalArgs = @("eval", $escCommand, $yamlFile) Write-Output...

Here is a `yq.ps1` that seems to act better. ```powershell Param( [string]$command, [string]$yamlFile ) $escCommand = $command -replace '"','\"' $evalArgs = @("eval", "$escCommand", $yamlFile) Write-Output ".\yq.exe" $evalArgs & ".\yq.exe" $evalArgs...

The main idea is to try, as best as is possible, to keep the connection near where it appeared before the removal of the pointer value. So, here is what...

Yes, webhooks could be used to capture the browser generated commits. What would the mechanism be for injecting commits, e.g. replay recorded commits?