Josh Rabinowitz

Looks good! One suggestion: * put your new functions like `_check_if_plaintexts_have_conflicts` and `_check_if_plaintext_has_conflicts` in `src/_utils/_git_secret_tools.sh` * Your diff shows `git secret changes` with a new`-m` option. `-m` is already used...

This also seems pretty easy to script locally on your systems. Planning to close this ticket in a couple weeks unless there is more input.

I think it's ok if we stop testing Dancer on perl 5.10 and 5.12.

@bigpresh can I do anything to help port this over from dancer2 and test?

@bigpresh planning to test this in the next few days

Hey @sobolevn we talked about doing this on Jun 17, any thoughts on this topic?

@mihaigalos you may be running into #925. git-secret expects to be used from the top-level directory of a repo, then revealing a secret like subdir/config.txt.secret should work (we have tests...

@pcgeek86 can you submit a PR automating adding this package to Scoop?

I volunteer to help, if desired too.

After reading this report more carefully, it appears as if git-secret is correct that the file `functions/.runtimeconfig.json.secret` does not exist because `git secret hide` was never run Nevertheless, doing the...