From 5d48020ef6aa211ba950bf9faa73d026a6cec61e Mon Sep 17 00:00:00 2001 From: hahwul Date: Mon, 30 Oct 2023 00:53:59 +0900 Subject: [PATCH] Update rubocop config --- .github/workflows/rubocop.yml | 2 ++ .rubocop.yml | 10 ++++++++++ 2 files changed, 12 insertions(+) create mode 100644 .rubocop.yml diff --git a/.github/workflows/rubocop.yml b/.github/workflows/rubocop.yml index 2b76fa3..9cd5c5a 100644 --- a/.github/workflows/rubocop.yml +++ b/.github/workflows/rubocop.yml @@ -9,5 +9,7 @@ jobs: - uses: actions/checkout@v1 - name: RuboCop Linter uses: andrewmcodes/rubocop-linter-action@v3.3.0 + with: + action_config_path: ".rubocop.yml" env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} diff --git a/.rubocop.yml b/.rubocop.yml new file mode 100644 index 0000000..cc4712a --- /dev/null +++ b/.rubocop.yml @@ -0,0 +1,10 @@ +# The behavior of RuboCop can be controlled via the .rubocop.yml +# configuration file. It makes it possible to enable/disable +# certain cops (checks) and to alter their behavior if they accept +# any parameters. The file can be placed either in your home +# directory or in some project directory. +# +# RuboCop will start looking for the configuration file in the directory +# where the inspected file is and continue its way up to the root directory. +# +# See https://docs.rubocop.org/rubocop/configuration