Stavros Ntentos

I think it will be better to just go with `"NO_COLOR" in os.environ and os.environ["NO_COLOR"]` (or, I'd simplify it as `os.environ.get("NO_COLOR") is not None`). Same with `FORCE_COLOR`. So, we end...

I didn't test it with code yet - but I promise that thin wrapper will have explicit tests 😅

On a tangent, I'd like "multiple examples" (in the "test-driven development" sense)

It doesn't happen. That's how I moved on - did the command (and its resolution) by terminal. I think it may be related to the fact that, the stash being...

_btw, on a tangent: maybe rename `-filter=added` to `-filter=lines`?_ _I think the series `line`, `diff_context`, `file`, `nofilter` fits better together than the "ambiguous" `added`_

... and one for [Why you shouldn't use ENV variables for secret data](https://web.archive.org/web/20250413172028/https://blog.diogomonica.com//2017/03/27/why-you-shouldnt-use-env-variables-for-secret-data/)

tl;dr the correct specification should be ```ruby spec.add_dependency "webrick", "~> 1.8", ">= 1.8.2" ``` fixing it here (and pushing it) does not preclude doing https://github.com/rack/rackup/issues/12. ... but it does help...

> does not make rackup stop working with it. What does that mean? 😅 > restrictivly pin in your own gemfile if necessary Pinning a transitive dependency means requiring it....

My Tampermonkey was stuck to 2.5.9, because it was stuck to the old (?) https://update.greasyfork.org/scripts/423851/Simple%20YouTube%20Age%20Restriction%20Bypass.user.js update URL. "Re-installing" updates to 2.5.10 (see README.md), and works ✌️