| 16:17 | <Chris de Almeida> | https://github.com/tc39/how-we-work/pull/111 |
| 16:18 | <Chris de Almeida> | PR to fix a bunch of markdown issues and move the template code to a code block |
| 16:19 | <Chris de Almeida> | next one I will have will fix the alpha order of terms (and add the alpha order requirement in the contribution section) |
| 16:53 | <bakkot> | if markdownlint is actually good (I have not used it), we should maybe set it up in CI? |
| 17:15 | <rkirsling> | yeah this was the first I'd heard of it but it seems wise |
| 18:02 | <Chris de Almeida> | I've been using it for 6 years or so. it's great, but I've never bothered to add it to any CI because it's md and not quite "code", but that's a good idea |
| 18:07 | <Kris Kowal> | Missed opportunity for “Lint, M.D.” pun. |
| 18:22 | <ljharb> | +1 for adding it to CI; i use evalmd in many of my projects in CI to ensure that code examples execute successfully, and linting markdown also seems useful |
| 18:47 | <Chris de Almeida> | I wouldn't mind setting it up, but I lack the requisite permissions on the repo |
| 18:48 | <bakkot> | you should be able to just send a PR adding a github action? I don't think you need permissions beyond that |
| 18:49 | <Chris de Almeida> | ah, true. I was thinking more about configuring status checks, etc |
| 19:02 | <ljharb> | i can configure them once it's merged |
| 20:40 | <Chris de Almeida> | https://github.com/tc39/how-we-work/runs/7347701399?check_suite_focus=true |
| 20:41 | <Chris de Almeida> | linting github action added. see test result ☝️ |