Developer docs

This section is for contributors and maintainers of eslint-plugin-github-actions-2.

Start here

• 🚀 Maintainer quickstart
• 🧱 Architecture overview
• 🧭 Guides
• 📐 Architecture Decision Records
• 🛠️ Maintenance playbooks
• 👨‍💻 Developer API reference
• 🔎 ESLint Config Inspector
• 🎨 Stylelint Config Inspector

Scope

Developer docs cover:

• local setup and day-to-day development workflow
• plugin architecture and core data flow
• rule authoring/testing patterns
• release and docs pipeline operations
• architecture decisions and rationale

Contribution flow

1. Start from a feature branch.
2. Implement or adjust rule/docs/tests.
3. Run local quality checks (typecheck, tests, docs build).
4. Open a PR with clear rationale and migration notes if needed.

For external contributors, see the repository-level CONTRIBUTING.md.