Todd Wolfson

Additionally, there was a bug in the installer that should be patched in pose/webdriver-manager#14

Alright, after a bit of working around errors. We got both a non-symlink version working with the code that @gbmhunter posted (once the pose/webdriver-manager#14 patches are landed). Here are the...

I took a shot at this tonight. I couldn't find anything straightforward with `.gitattributes` but following @jvehent's suggestion, I started on a custom merge configuration for SOPS. Here's a proof...

Upon reviewing my code, the `.git/config` + `.gitattributes` are more designed for automatic dependency resolution when running `git merge` (there shouldn't be a mergetool window open, it's all supposed to...

Outside of that I have a couple more notes: - For replacing an entire file's contents, we should be able to accept input from STDIN but I don't think it...

With respect to STDIN, is `foo.yaml` raw data (e.g. `foo: bar`)? If so, how does `sops -e` know which keys to use when outputting content? With respect to `sops --show_master_keys`,...

Ah, I have answered my own question in both respects. `-e` accepts data that already has a `sops` key and will use that as its keys https://github.com/mozilla/sops/blob/f63597f901f50f07ff72452b4bdb485518b85de7/sops/__init__.py#L511-L516 So the answers...

Alright, I explored `git-mergetool`. Unfortunately, we would need to have users set up `.git/config` with a `[mergetool "sops-mergetool"]` to get it working. That being said, the gist is now focused...

After thinking for a bit, there's no reason why that script has to be used via `git mergetool` (and consequently configured via `.git/config`). As I learned during iterations, we can...

A few lines down from `chrome.storage.sync` settings is `chrome.storage.local`. The limitation there is 5MB instead of 100KB total, definitely more reasonable: https://searchfox.org/mozilla-central/rev/8d55e18875b89cdf2a22a7cba60dc40999c18356/toolkit/components/extensions/schemas/storage.json#341-351