This is generalized lint reporter action

Focuses on:

• Many lint file format support
• Flexible extendable reporting
• Multiple report format support, as check-run, comment or inline-comment

Current supporting lint file format:

Now, this action is WIP. Features are not enough and should improve about transformer and operator. If you have nice idea, please send as issue:heart:

This action have 3 steps. Flexible and extendable are realized by separating step

1. Transform lint report file to common lint format file
2. Operate converting common lint file
3. Report common lint to GitHub

name: CI

on:
  pull_request:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v1
        with:
          node-version: 12
      - run: npm install
      - run: npm run build
      - run: npm run lint
        continue-on-error: true
      - uses: MeilCli/common-lint-reporter/transformer/eslint@0
        with:
          # your output path
          report_files: |
            eslint_report.json
      - uses: MeilCli/common-lint-reporter/operator/filter-by-file-changed@v0
      - uses: MeilCli/common-lint-reporter@v0
        with:
          report_type: 'check_run'
          report_name: 'Lint Report'

• General
  • Usage of oss or using dependabot repository
  • Report lint result
• Transformer
  • androidlint
  • checkstyle
  • dotnet format
  • eslint
  • junit
  • markdownlint
  • RuboCop
  • stylelint
  • textlint
• Operator
  • add
  • distinct
  • filter
  • filter-by-file-changed
  • map
• Reference
  • Lint result file format
  • Operator context

MIT License

• actions/toolkit, published by MIT License
• apollo-client, published by MIT License
• cross-fetch, published by MIT License
• graphql, published by MIT License
• fast-xml-parser, published by MIT License
• he, published by MIT License