https://nick2bad4u.github.io/eslint-plugin-github-actions-2/blog eslint-plugin-github-actions-2 Blog 2026-03-21T00:00:00.000Z https://github.com/jpmonette/feed eslint-plugin-github-actions-2 Blog https://nick2bad4u.github.io/eslint-plugin-github-actions-2/img/logo.svg <![CDATA[Docs polish pass (developer docs, sidebar, and IA)]]> https://nick2bad4u.github.io/eslint-plugin-github-actions-2/blog/docs-polish-pass 2026-03-21T00:00:00.000Z We shipped a docs polish pass focused on developer experience:

  • upgraded developer information architecture and sidebar structure
  • added maintainer guides and ADR documentation pages
  • improved docs home with clear user-vs-maintainer paths
  • improved navigation to the TypeDoc developer API reference

This pass also reinforces docs as a first-class deliverable, not only rule pages.

]]> Nick2bad4u https://github.com/Nick2bad4u <![CDATA[Maintainer workflow baseline]]> https://nick2bad4u.github.io/eslint-plugin-github-actions-2/blog/maintainer-workflow-baseline 2026-03-21T00:00:00.000Z To keep contributions predictable and high-signal, our baseline maintainer loop is:

  1. implement changes in src/ and corresponding tests in test/
  2. update user/developer docs for any observable behavior shift
  3. run typecheck, lint, tests, and docs build before opening PR

By treating docs, metadata, and tests as one unit, we reduce drift and make releases safer.

]]> Nick2bad4u https://github.com/Nick2bad4u