Henry Bley-Vroman

This project's been gathering cobwebs for a few years now. It's broken in a couple ways. I'm still excited about the idea. Aiming to dust it off and modernize it...

see https://css-tricks.com/probably-dont-base64-svg/ and https://codepen.io/tigt/post/optimizing-svgs-in-data-uris

missing unsupported-nested-javascript documentation

4

In a dry run I get ``` error[unsupported-nested-javascript]: referenced a JavaScript module without type declarations from a TypeScript module --> # … = hint: add a type declaration (d.ts) for...

A widespread Markdown extension is footnotes. See https://www.markdownguide.org/extended-syntax/#footnotes. It'd be great if READMEs supported a footnote extension. Compare e.g. https://jsr.io/@olets/css-fluid-length, where footnote-y syntax becomes in-place links, and https://codeberg.org/olets/css-fluid-length, where the...

Throughout this repo, links are provided to the archived repo https://github.com/EthicalSource/hippocratic-license rather than this repo https://github.com/EthicalSource/hippocratic-license-3

Maybe by default? Or maybe another top-level config, `rebase-fork-point`? Or more generally some way to pass Git flags? ```yaml rebase: branch-a: - branch: branch-b config: --fork-point ```

Before rebasing, check to see if `` and/or `` are behind/diverged from its upstream. If it has, prompt to pull.