One change, many repositories
Link every repository a product is built from, and a change that spans them is planned, built and merged as one initiative.
Most products are more than one repository: an API and the web app that calls it. Taiga worked on one repository per product, so a change spanning two had to be split and coordinated by hand.
A product now links all of its repositories, and Taiga treats them as one product's code. An initiative that changes several is one plan and one run, with a pull request in each repository. Nobody is asked to review half a change. The pull requests stay drafts until the work in every repository is ready, then become ready for review together, each listing the others in the order they merge. With autonomous merge, Taiga merges them in that order, each under its own repository's rules.
Imports read the repositories together, sweeps cover each one, and Deployments shows what is running in production per repository.
A new endpoint in the backend and the screen that calls it in the frontend arrive as one initiative, and the backend merges first.
Taiga works on your product as it is built, not one repository at a time.
Every change, dated the day it shipped.
Dated the day they shipped, newest first.
