pipeline-kit

Reusable GitHub Actions and workflows for Blueshoe projects.

Available Actions

Action	Description	Docs
eslint-js-prefix	Enforce js- prefix for DOM selectors	Details
security-gitleaks	Secret detection	🔜 Planned
security-python-audit	Python dependency vulnerabilities	🔜 Planned

---

eslint-js-prefix

Enforces that JavaScript DOM selectors use a js- prefix to decouple your code from CSS frameworks.

// ❌ Breaks when CSS framework updates
document.querySelector('.btn-danger')

// ✅ Independent of CSS
document.querySelector('.js-delete-button')

Quick Start

- uses: Blueshoe/pipeline-kit/actions/eslint-js-prefix@v1

Common Use Cases

# Custom prefix
- uses: Blueshoe/pipeline-kit/actions/eslint-js-prefix@v1
  with:
    prefix: 'hook-'

# Additional allowed patterns
- uses: Blueshoe/pipeline-kit/actions/eslint-js-prefix@v1
  with:
    allowed-patterns: '["^my-component-"]'

# Warn instead of fail
- uses: Blueshoe/pipeline-kit/actions/eslint-js-prefix@v1
  with:
    severity: 'warn'

# Specific directory
- uses: Blueshoe/pipeline-kit/actions/eslint-js-prefix@v1
  with:
    working-directory: './frontend'

📖 Full Documentation – All inputs, outputs, framework detection, and examples.

---

Versioning

# Recommended: Latest v1.x.x
uses: Blueshoe/pipeline-kit/actions/eslint-js-prefix@v1

# Pinned version
uses: Blueshoe/pipeline-kit/actions/eslint-js-prefix@v1.2.3

Contributing

1. Fork & create feature branch
2. Make changes
3. Run tests: cd actions/eslint-js-prefix/plugin && npm test
4. Submit PR

We use Conventional Commits:

• fix: → Patch (v1.0.0 → v1.0.1)
• feat: → Minor (v1.0.0 → v1.1.0)
• feat!: → Major (v1 → v2)

License

MIT