◇ Could this help me?
Yes. Per-branch preview URLs are a real feature of the major hosting platforms and this is genuinely a short setup, so the payoff-to-effort ratio is unusually good. One thing to add that the video leaves out: staging is only a real test if it uses its own database and its own API keys, because a preview environment pointed at production data can cause exactly the incident it was set up to prevent. This is a general practice.
Set up three environments for this project. Configure the main branch as production with direct pushes blocked, a development branch as the working environment, and per-branch preview deployments so every branch gets its own URL. Critically, give the non-production environments their own database and their own API keys rather than pointing them at production, and show me exactly where each environment's configuration is set. Then write me a short deploy checklist covering test, review the diff, merge, and verify.