eslint-plugin-github-actions-2 Blog https://nick2bad4u.github.io/eslint-plugin-github-actions-2/blog eslint-plugin-github-actions-2 Blog Sat, 21 Mar 2026 00:00:00 GMT https://validator.w3.org/feed/docs/rss2.html https://github.com/jpmonette/feed en <![CDATA[Docs polish pass (developer docs, sidebar, and IA)]]> https://nick2bad4u.github.io/eslint-plugin-github-actions-2/blog/docs-polish-pass https://nick2bad4u.github.io/eslint-plugin-github-actions-2/blog/docs-polish-pass Sat, 21 Mar 2026 00:00:00 GMT 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.

]]> docs docusaurus typedoc <![CDATA[Maintainer workflow baseline]]> https://nick2bad4u.github.io/eslint-plugin-github-actions-2/blog/maintainer-workflow-baseline https://nick2bad4u.github.io/eslint-plugin-github-actions-2/blog/maintainer-workflow-baseline Sat, 21 Mar 2026 00:00:00 GMT 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.

]]> maintainers workflow quality