app/Traits/Form/CodeQuality.php:

• [x] add in public $stepPhpstanUseNeon; // false
• [x] in loadDefaultsCodeQuality() set as false
• [x] in loadCodeQualityFromJson set data_fill($j, "stepPhpstanUseNeon", false); for backward compatibility
• [x] set in setDataCodeQuality function

resources/views/livewire/form/code-quality.blade.php

• [x] add a checkbox

resources/views/yaml/code_quality.blade.php

• [x] add the new if statement case

Run php artisan migrate
  php artisan migrate
  shell: /usr/bin/bash -e {0}
  env:
    DB_CONNECTION: mysql
    DB_DATABASE: db_test_laravel
    DB_PORT: 33306
    DB_USER: root
    DB_PASSWORD: DB_PASSWORD

   Illuminate\Database\QueryException 

  SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution (SQL: select * from information_schema.tables where table_schema = db_test_laravel and table_name = migrations and table_type = 'BASE TABLE')

  at vendor/laravel/framework/src/Illuminate/Database/Connection.php:692
    688▕         // If an exception occurs when attempting to run a query, we'll format the error
    689▕         // message to include the bindings with SQL, which will make this exception a
    690▕         // lot more helpful to the developer instead of just the database's errors.
    691▕         catch (Exception $e) {
  ➜ 692▕             throw new QueryException(
    693▕                 $query, $this->prepareBindings($bindings), $e
    694▕             );
    695▕         }
    696▕     }

      +36 vendor frames 
  37  artisan:37
      Illuminate\Foundation\Console\Kernel::handle()
Error: Process completed with exit code 1.

Not sure where to start with this?

Now we have https://github.com/Hi-Folks/gh-actions-yaml-generator/blob/main/ghygen-github-actions-yaml-generator-laravel.png as cover image.

Any suggestion for the new cover ?

Hey there! 🖐 This is my first PR.

Summary

The goal for this PR is use view composer by Laravel Framework, remove $data varible and passes the info using view composer.

#103

Hi,

I am not sure if you are looking for deployment options for this generator but I made the Ploi Deploy Action that triggers the Ploi.io webhook or API and deploys your application to the server.

Let me know if you need more information 😄

Add an option with phpstan selection, for using phpstan.neon instead of hardcoded value (like the level). In file app/Traits/Form/CodeQuality.php:

• [ ] add in public $stepPhpstanUseNeon; // false
• [ ] in loadDefaultsCodeQuality() set as false
• [ ] in loadCodeQualityFromJson set data_fill($j, "stepPhpstanUseNeon", false); for backward compatibility
• [ ] set in setDataCodeQuality function

in resources/views/livewire/form/code-quality.blade.php

• [ ] add a checkbox

in resources/views/yaml/code_quality.blade.php add the case

@if ($stepToolStaticAnalysis == 'phpstan')

for the

vendor/bin/phpstan analyse {{ $stepDirStaticAnalysis }} --level=4 --no-progress

in order to produce something like

	    - name: Execute Code Static Analysis (PHP Stan)
      run: |
        vendor/bin/phpstan analyse src --level=4 --no-progress

with the option "use phpstan.neon":

	    - name: Execute Code Static Analysis (PHP Stan)
      run: |
        vendor/bin/phpstan analyse -c phpstan.neon --no-progress

Replace Requirements section in CONTRIBUTING.md file with:

## Open a Pull Request

In order to maintain consistency in the source code we are following PSR12 coding standard, and using PHP stan for static code analysis.
You can use the command:

make allcheck

to launch
- **[PSR-12 Coding Standard](https://www.php-fig.org/psr/psr-12/)**, under the hood is used [PHP Code Sniffer](https://pear.php.net/package/PHP_CodeSniffer);
- **PHPstan** with [level 5](https://phpstan.org/user-guide/rule-levels)
- **Phpunit** to execute all tests from ./tests/*

I suggest to launch *make allchecks* before to commit or before to create PR.

If you want to work on a PR, I suggest you to creating a new branch starting from **develop branch**, and use it also when you will submit your new **P**ull **R**equest on the original repository.

If you want to contribute with an high quality PR, I suggest you to focus not just on the source code but also:

- **Add tests!** - Your patch won't be accepted if it doesn't have tests.

- **Document any change in behaviour** - Make sure the `README.md` and any other relevant documentation are kept up-to-date.

- **Consider our release cycle** - We try to follow [SemVer v2.0.0](https://semver.org/). Randomly breaking public APIs is not an option.

- **One pull request per feature** - If you want to do more than one thing, send multiple pull requests.

- **Send coherent history** - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please [squash them](https://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages) before submitting.

Using the actions https://github.com/marketplace/actions/the-php-security-checker , add a job in theGithHub Actions workflow for executing security check.

• executing on every push

on:
  push:
    branches:
      - main
      - develop
      - features/**

• scheduling at 7:30 am and 5:30pm

on:
  schedule:
    - cron:  '30 7,17 * * *'

• steps are: checkout and using the security check action:

steps:
    - uses: actions/checkout@v2
    - uses: symfonycorp/security-checker-action@v2

We spoke on Twitter briefly in the week after you pointed out this generator. I was thinking it might be a cool idea if instead of needing to select things via a form that could automate a lot of the option selections using just the info from composer.json?

Detect the PHP version(s), Laravel version etc. and which PHP tools are involved and then just provide a set of appropriate actions to tick. At that point I'd probably even be happy to pay for it as a service if it saved me the time of having to work out which things I could have in my pipeline without the research.

Just a thought anyways.

Using the latest version, tried generating a YAML file..

Error
Reference "" does not exist at line 1 (near "- *").
There was some error during validation. Take a look about your data in the form:
Reference "" does not exist at line 1 (near "- *").

Renders out this YAML file:

name: Template - Laravel application (Mysql)
on:
  push:
    branches:
      - master
      - staging
      - testing
      - production
      - develop
      - features/**
      - updates/**
      - update/**
      - fix/**
      - patch/**
  pull_request:
    branches:
      - *
 
jobs:
  laravel-tests:
    runs-on: ubuntu-latest
# Service container Mysql mysql
    services:
      # Label used to access the service container
      mysql:
        # Docker Hub image (also with version)
        image: mysql:5.7
        env:
          MYSQL_ROOT_PASSWORD: secret
          MYSQL_DATABASE:  homestead
        ## map the "external" 33306 port with the "internal" 3306
        ports:
          - 33306:3306
        # Set health checks to wait until mysql database has started (it takes some seconds to start)
        options: >-
          --health-cmd="mysqladmin ping"
          --health-interval=10s
          --health-timeout=5s
          --health-retries=3
 
    strategy:
      matrix:
        operating-system: [ubuntu-latest]
        php-versions: [ '8.0','7.4' ]
        dependency-stability: [ prefer-stable ]
 
    name: P${{ matrix.php-versions }} - L${{ matrix.laravel }} - ${{ matrix.dependency-stability }} - ${{ matrix.operating-system}}
 
    steps:
    - uses: actions/checkout@v2
    - name: Setup Node.js
      uses: actions/setup-node@v1
      with:
        node-version: '15.x'
    - name: Cache node_modules directory
      uses: actions/cache@v2
      id: node_modules-cache
      with:
        path: node_modules
        key: ${{ runner.OS }}-build-${{ hashFiles('**/package.json') }}-${{ hashFiles('**/package-lock.json') }}
    - name: Install NPM packages
      if: steps.node_modules-cache.outputs.cache-hit != 'true'
      run: npm ci
    - name: Build frontend
      run: npm run development
    - name: Install PHP versions
      uses: shivammathur/setup-php@v2
      with:
        php-version: ${{ matrix.php-versions }}
    - name: Get Composer Cache Directory 2
      id: composer-cache
      run: |
        echo "::set-output name=dir::$(composer config cache-files-dir)"
     - uses: actions/cache@v2
      id: actions-cache
      with:
        path: ${{ steps.composer-cache.outputs.dir }}
        key: ${{ runner.os }}-composer-${{ hashFiles('**/composer.lock') }}
        restore-keys: |
          ${{ runner.os }}-composer-
     - name: Cache PHP dependencies
      uses: actions/cache@v2
      id: vendor-cache
      with:
        path: vendor
        key: ${{ runner.OS }}-build-${{ hashFiles('**/composer.lock') }}
    - name: Copy .env
      run: php -r "file_exists('.env') || copy('.env.example', '.env');"
    - name: Install Dependencies
      if: steps.vendor-cache.outputs.cache-hit != 'true'
      run: composer install -q --no-ansi --no-interaction --no-scripts --no-progress --prefer-dist
 
    - name: Generate key
      run: php artisan key:generate
    - name: Directory Permissions
      run: chmod -R 777 storage bootstrap/cache
    - name: Run Migrations
# Set environment
      env:
        DB_CONNECTION: mysql
        DB_DATABASE: homestead
        DB_PORT: 33306
        DB_USER: root
        DB_PASSWORD: secret
 
      run: php artisan migrate
 
    - name: Show dir
      run: pwd
    - name: PHP Version
      run: php --version
 
# Code quality
    - name: Execute tests (Unit and Feature tests) via PHPUnit
# Set environment
      env:
        DB_CONNECTION: mysql
        DB_DATABASE: homestead
        DB_PORT: 33306
        DB_USER: root
        DB_PASSWORD: secret
 
      run: vendor/bin/phpunit --testdox
 
    - name: Execute Code Sniffer via phpcs
      run: |
        composer require --dev squizlabs/php_codesniffer
        vendor/bin/phpcs --standard=PSR12 app
 
    - name: Execute Code Static Analysis (PHP Stan + Larastan)
      run: |
        composer require --dev nunomaduro/larastan
        vendor/bin/phpstan analyse app -c ./vendor/nunomaduro/larastan/extension.neon  --level=4 --no-progress
 
 
 
 
    - name: Browser Test - upgrade and start Chrome Driver
      run: |
        composer require --dev laravel/dusk
        php artisan dusk:chrome-driver --detect
        ./vendor/laravel/dusk/bin/chromedriver-linux > /dev/null 2>&1 &
     - name: Run Dusk Tests
      run: |
        php artisan serve > /dev/null 2>&1 &
        chmod -R 0755 vendor/laravel/dusk/bin/
        php artisan migrate
        php artisan dusk
 # Set environment
      env:
        DB_CONNECTION: mysql
        DB_DATABASE: homestead
        DB_PORT: 33306
        DB_USER: root
        DB_PASSWORD: secret

We love the idea of ​​the project to generate the yml file, it would be interesting to add support for other types of banks besides MySQL.

• [x] PostgreSQL
• [ ] MS SQL Server
• [x] SQLite
• [ ] Mongo or another NoSQL

Thnks!

As discussed briefly with my friend @AlessandroMinoccheri at PHPDay2022 event, it would be nice to add "Symfony staff". Something like "Laravel Stuff". This is just a placeholder as a reminder. For now, I'm going to start investigate which steps are needed and are specific for a Symfony application.