Code Quality Checks and Deployment with GitHub Actions

“The XP philosophy is to start where you are now and move towards the ideal. From where you are now, could you improve a little bit?” Kent Beck Table of Contents Introduction Overview: Two-Workflow Strategy (Quality Gate + Deploy) Workflow 1: Code Quality Checks (PR → stg) Workflow 2: Deploy (push → stg) Practical Setup (Step-by-step) FAQs Key Takeaways Conclusion 1. Introduction This document explains a practical GitHub Actions setup that enforces Flutter code quality checks on every pull request to the stg branch and deploys the Flutter web build to AWS S3 whenever code is pushed to stg. The approach uses two separate workflows: Code Quality Checks: runs on pull_request events (stg) Deploy (stg): runs on push events to stg 2. Overview: Two-Workflow Strategy (Quality Gate + Deploy) Developers open a Pull Request targeting stg. GitHub Actions runs Flutter clean → pub get → analyze → test. If checks pass, the PR is safe to merge. If checks fail, a Rocket.Chat alert is sent with the buil