Create a GitHub Actions CI/CD Workflow for Automated Testing and Deployment

Create a production-ready GitHub Actions workflow file (.yml) for a [LANGUAGE/FRAMEWORK] project hosted on GitHub. The workflow should automate the CI/CD pipeline with the following requirements: 1. **Trigger Configuration**: Set up triggers for push events on the [BRANCH_NAME] branch and pull requests targeting that branch. Include a manual workflow_dispatch trigger with an input parameter for selecting the deployment environment ([ENVIRONMENTS_LIST]). 2. **Build & Test Job**: - Use [RUNNER_OS] as the runner. - Check out the code and set up the [LANGUAGE/FRAMEWORK] environment with version [VERSION]. - Cache dependencies (e.g., node_modules, pip cache, or Maven .m2) to speed up builds. - Install dependencies and run the full test suite. - Generate a test coverage report and upload it as an artifact. 3. **Linting & Static Analysis Job**: Run [LINTING_TOOL] in parallel with the build job to enforce code quality standards. 4. **Deploy Job**: - This job should only run after both the build and lint jobs succeed. - Only deploy when the event is a push to [BRANCH_NAME] (not on PRs). - Deploy to [DEPLOYMENT_TARGET] (e.g., AWS, Vercel, Docker Hub, GCP). - Use GitHub Secrets for all sensitive credentials — list which secrets need to be configured. 5. **Notifications**: Add a final job that sends a [NOTIFICATION_CHANNEL] notification (e.g., Slack, email, Discord) on both success and failure, including the commit SHA and author. 6. **Security & Best Practices**: Pin all third-party actions to specific SHA commits, use least-privilege permissions with the permissions key, and add concurrency controls to prevent duplicate runs. Provide the complete YAML file with inline comments explaining each section. After the file, include a setup checklist of repository secrets and settings that need to be configured.