🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко)

Nice! I'm pretty sure that someone would find interesting non-technical notes as well... As for separation of technical notes, I may suggest just forking the repo and removing non-technical from...

Fair enough. I can drop autodetection for now and will try to add some docs on that.

Oh, and I'd add that `.com.` is also valid but probably the average user doesn't know about it :) Still I'd strip dots on both sides of the string.

# If somebody is looking to monkey-patch it in their project — just apply this 👇                 https://github.com/sanitizers/octomachinery/commit/e5756d9ad21cb77ed138bcf865eea0eb9efcd03b

@bitprophet bump :alarm_clock:

Dunno, I don't think I use the theme anymore, or Travis for that matter. It should be fine to just replace with `.com` tho. OTOH it's probably more important to...

Ah.. was just about to create the same issue. Occurrences in two docs sites I maintain (there's much more): - https://multidict.readthedocs.io - https://molecule.readthedocs.io And this misleading button was there since...

Done: https://github.com/bitprophet/alabaster/pull/147 # UPD: If somebody is looking to monkey-patchit in their project while this isn't merged — just apply this 👇                 https://github.com/sanitizers/octomachinery/commit/e5756d9ad21cb77ed138bcf865eea0eb9efcd03b

Maybe inject black fixup commits in between user-created ones? This way the user could attempt to squash related things fairly easily if they want it... P.S. I also do not...

You can try injecting two commits, not one. Fixup + its revert. This would probably simplify the interactive rebase part. Then, you could squash those reverts with the following commits......