workflow: dogfood & tidy

[casperdcl]

• minify/tidy/lint workflows
• bump actions versions
• CML dogfooding
• make releases --draft

[dacbd]

I am personally not a fan of the {} syntax in yaml, additionally its even less commonly seen in the scope of GitHub Actions.

[0x2b3bfa0]

I am personally not a fan of the {} syntax

I wholeheartedly agree: it's :purugly:

[casperdcl]

personally not a fan of the {} syntax

-Wnot-using-a-legitimate-feature? This syntax exists for precisely this use case (short one-liner unlikely to change).

less commonly seen in the scope of GitHub Actions

fallacious, scanadlous!

[0x2b3bfa0]

-Wnot-using-a-legitimate-feature

For the same reason some code files contain line breaks, even if they don't have to: readability.

[casperdcl]

For the same reason some code files contain line breaks

Still not right - an accurate analogy would be refusing to use line breaks. Refusing to use a feature regardless of scenario is inexplicable.

readability

yes, maximising that here. Also not using {} where it doesn't make sense/harms readability. Also the linter is v. happy with the proposed use of {} :)

[tasdomas]

Re {} - that syntax has limited (very limited) uses in yaml, imho. Linters are not raising issues because valid json is valid yaml.

[casperdcl]

dropped {} by popular demand

Also pushed some docstring edits after a thorough review (related to iterative/cml.dev#324) - please do check /CC @0x2b3bfa0 will move to separate PR

[0x2b3bfa0]

Thanks! 🤺 🤝