Your branch, your pipelines
Taiga fits into the delivery process you already run: it works on the branch your team chooses and leaves infrastructure and pipelines to the teams that own them.
Most engineering organizations already have a delivery process: environment branches, required approvals, and platform teams that own infrastructure and pipelines. A tool that assumes it can ship straight to production, or bring its own pipelines, has to be worked around.
Taiga now works inside that process. Choose the branch it works on and every change it makes lands there. A team that promotes from development to staging to production points Taiga at development and keeps releasing exactly as it does today. Your branch protection still applies to everything Taiga opens, so the approvals your process requires still happen.
Whether Taiga also writes infrastructure code and CI/CD pipelines is set once for the organization and can be changed per product. Where a platform team already owns them, turn them off: Taiga builds the product to run on the platform you have, and your pipelines ship it. Adopting Taiga does not mean changing how you release.