project and project-staging) sharing the same codebase. one is for prod and one for staging/next. (as a reminder, with trunk-based approach you have only one branch + many feature branches, so having a permanent 'staging' branch is not allowedstaging and connected it to the staging project, whilst the root branch connects to the prod project.staging DB is a clone of the production, then there would be cases where we risk unwanted effects on real users. For example, if I have a marketplace where Alice is selling a hat and I clone the production DB on staging to test by purchasing of that hat, (the real) Alice will receive a email notifying her about the sale of that item, even if that happened only on staging. What are good practices to avoid such cases?