title: Github action did not make sqlfluff linting changes to a file
body: <p>I am trying to set sqlfluff linting for dbt files by following the example on <a href="https://discourse.getdbt.com/t/running-sqlfluff-fix-on-prs-as-a-github-action-with-inline-suggestions/4174" rel="nofollow noreferrer">this example</a> with some slight changes. My github actions yml file looks like:</p>
  <pre><code>name: Run sqlfluff linter
  
  on:
    push:
        branches:
          - main
          - sqlfluff_ga2
    
  jobs:
    sql-lint:
      name: runner / sqlfluff (github-check)
      runs-on: ubuntu-latest
      steps:
        - uses: actions/checkout@v2
        - uses: yu-iskw/action-sqlfluff@v3
          id: lint-sql
          with:
            github_token: ${{ secrets.github_token }}
            reporter: github-pr-review
            sqlfluff_version: &quot;1.2.0&quot;
            sqlfluff_command: &quot;lint&quot; # Or &quot;fix&quot;
            config: &quot;${{ github.workspace }}/.sqlfluff&quot;
            paths: '${{ github.workspace }}/models'
            github_base_ref: &quot;main&quot;
        - name: 'Show outputs (Optional)'
          shell: bash
          run: |
            echo '${{ steps.lint-sql.outputs.sqlfluff-results }}' | jq -r '.'
            echo '${{ steps.lint-sql.outputs.sqlfluff-results-rdjson }}' | jq -r '.'
  </code></pre>
  <p>and here is my <code>.sqlfluff</code> rules:</p>
  <pre><code>[sqlfluff]
  dialect = bigquery
  
  # L031 - Exclude rule requiring fully-qualified table names in joins
  # should have been disabled for BigQuery already
  # L036 - multiple SELECT columns can appear on the SELECT line
  # L051 - Exclude rule requiring INNER JOIN rather than just JOIN
  # L003 - Ignore whitespace problems for now
  # L034 - Don't move around columns
  # L016 - Long lines are fine
  # L009 - No need for a single newline at end of file
  # L008 - No need for spaces around commas
  exclude_rules = L051,L031,L036,L003,L034,L016,L009,L008
  
  [sqlfluff:rules:L010]
  # Keywords
  capitalisation_policy = upper
  </code></pre>
  <p>and finally here is a test sql file content which resides in models folder of the dbt file structure:</p>
  <pre><code>select
    t.table_catalog t_catalog,
    t.table_schema t_schema,
    t.table_name t_name,
    t.table_type t_type,
    c.column_name c_name,
    c.data_type d_type
  FROM &quot;{{ database }}&quot;.information_schema.tables t
  inner JOIN &quot;{{ database }}&quot;.information_schema.columns c
    on c.table_schema = t.table_schema
    and c.table_name = t.table_name
  where t.table_catalog =  '{{ database.upper() }}' 
    and t.table_type in ('BASE TABLE', 'VIEW') and t.table_schema = '{{ schema.upper() }}' and t.table_name = '{{ alias.upper() }}' 
  ORDER BY t.table_schema,
   t.table_name;
  
  </code></pre>
  <p>The github action run is successful, however, the sql file linting is not fixed. No capitalization or addition of <code>AS</code>alias took place. Here is the output I am seeing:
  <a href="https://i.stack.imgur.com/17r92.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/17r92.png" alt="outputfile" /></a></p>
  <p>I was wondering if someone can help me understand what is going on.</p>