Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

GodziLaravel's avatar

Does this workflow correct ?

I decided to implement the CI/CD on my Laravel project.

I would like to know if this workflow is correct :

Here's a streamlined workflow from commit to deployment on the test server:

  1. Develop on add-button-feature branch.
  2. Commit and push changes to GitLab (CI/CD pipeline is triggered, runs tests, linting, etc., but no deployment yet).
  3. Create a Merge Request (MR) to merge add-button-feature into the test branch.
  4. Assign MR to a code reviewer.
  5. Code reviewer reviews and approves the MR.
  6. Code reviewer merges MR into test branch.
  7. CI/CD pipeline runs again on the test branch, including deployment steps.
  8. Deployment to test server happens after the merge, based on the pipeline configuration.

Is there something missing ?

Thanks

0 likes
2 replies
Aecy's avatar

Hello! Your workflow looks solid and aligns well with common CI/CD practices. However, here are a few additional points to consider:

Pipeline Stages

  1. Build ; compile your assets
  2. Test ; run all the tests
  3. Lint ; check your code quality with phpstan (I always use larastan with laravel)
  4. Deploy ; automate the deploy
1 like
tisuchi's avatar

@godzilaravel that is my idea:

  • Feature Branch Development
  • Commit and Push with CI/CD Trigger
  • Merge Request Workflow
  • Pipeline on test Branch
  • Deployment to Test Server
2 likes

Please or to participate in this conversation.