PRs & releasing

As mentioned in wiki/Navigating-this-codebase efforts have been made to ensure PR descriptions are detailed, with rationale and screenshots (where appropriate). This makes things much easier to understand when tracing back over the history of the code one might be working on. See main Guardian recommendations on PRs.

Releasing

Manage-frontend is built using GitHub actions. See .github/workflows/ci.yml and script/ci.sh.

This makes it visible in RiffRaff with the name support::manage-frontend as per riff-raff.yaml. Scheduled Deployments (0 30 7 ? * TUE *) and Continuous Deployment (on main) are configured for manage-frontend. Since manage runs on EC2 instances (see wiki/AWS-infrastructure) the riff-raff.yaml defines a cloudformation deployment step followed by a autoscaling deployment... fairly standard.

PROD deployments are tracked with PROUT using the /_prout endpoint defined in app/server/routes/core.ts and configured via .prout.json.

Once out it's worth keeping an eye on both server-side Sentry and client-side Sentry (you can subscribe to the alerts in the Sentry UI), as well as in CloudWatch Dashboard/Logs.