A GitHub Action to run StandardRB against your code and create annotations in the GitHub UI.

• ✅ StandardRB Action
  • 📄 Introduction
  • 💡 Usage
    • 📦 Example Workflow
  • ⚠️ Gotchas
  • 📸 Screenshots
  • 🔖 Changelog
  • 🆘 Contributing
  • 🚨 Code of Conduct
  • ©️ License
  • 🤖 Check Out My Other Ruby GitHub Actions
  • ✨ Contributors

GitHub Actions are an amazing new tool that can dramatically improve productivity while using the GitHub platform. While it is not hard to write a custom GitHub action to run StandardRB on your codebase, this action takes that functionality one step further using the checks API. After the StandardRB Linter Action runs StandardRB against your code, it will create annotations that you can easily view, matched up with the offending code.

Since GitHub actions and the checks API are continually changing, it is possible that there will be breaking API changes that affect this action. If so, please open an issue and I will look into it as soon as I can.

Add the following to your GitHub action workflow to use StandardRB Linter Action:

- name: StandardRB Linter
  uses: andrewmcodes/[email protected]
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Here is an example workflow file incorporating StandardRB Linter Action:

name: StandardRB

on: [push]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v1
    - name: StandardRB Linter
      uses: andrewmcodes/[email protected]
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Due to the GitHub Check Runs API, we can only return 50 annotations per run. See here for more info.

View our Changelog

Contributing Guide

Code of Conduct

MIT

• andrewmcodes/rubocop-linter-action.
• andrewmcodes/haml-lint-action.

Thanks goes to these wonderful people (emoji key):

Andrew Mason 🚇 📖 💻

This project follows the all-contributors specification. Contributions of any kind welcome!