name: Code style

on: [push, pull_request]

jobs:
    phpcs:
        name: PHPCS
        runs-on: ubuntu-latest
        steps:
            - name: Checkout
              uses: actions/checkout@v2

            - name: Setup PHP
              uses: shivammathur/setup-php@v2
              with:
                php-version: '7.4'

            - name: Install dependencies
              run: composer update --prefer-dist --no-progress --no-suggest

            - name: Run script
              run: vendor/bin/phpcs

name: Code style

on: [push, pull_request]

permissions:
  contents: read

jobs:
    phpcs:
        name: PHPCS
        runs-on: ubuntu-latest
        steps:
            - name: Checkout
              uses: actions/checkout@v2

            - name: Setup PHP
              uses: shivammathur/setup-php@v2
              with:
                php-version: '7.4'

            - name: Install dependencies
              run: composer update --prefer-dist --no-progress --no-suggest

            - name: Run script
              run: vendor/bin/phpcs

Set permissions for GitHub actions
chore: Set permissions for GitHub actions

 Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much.

- Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions

https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs

[Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)

Signed-off-by: nathannaveen <b37dc86ffc1291bdc2112c1c336789fc137c3957@users.noreply.github.com>
