William Entriken
William Entriken
An important part of having evergreen, reusable, set-it-once-and-forget-it GitHub Actions CI testing is having a `MOODLE_STABLE` branch in the official Moodle repository that is updated every time a major release...
It is *helpful* to test against new upstream releases. And this is best practice. Not testing against new upstream releases means that when I want to upgrade my Moodle 4.4...
Also I have a repro case for binary installations https://github.com/rubygems/rubygems/issues/6214 It may be a duplicate/specialization of #3290 but I wanted to spell it all out so there is a write-up...
This also affects: MD058/blanks-around-tables And FYI, kramdown supports these attributes **before** or after the content: ```md {: .lead} Hi ``` Try it yourself at: https://kramdown.electricbook.works/