This issue is to explore the feasibility and potential of running the CI of all downstream dependencies in our codebase each time an upstream dependency has a PR open.
The value being to reduce the number of cases where we need to revert changes because they introduce breaking changes or are simply too hard to migrate, so a more progressive approach needs to be taken.
Every time we change something in Angular, we open a pull request, we’re syncing the source code from the pull request to the Google internal mono repo, which has about 4,500 Angular applications there, some of them with millions of lines of code
React: running the CI for all Facebook.com on each change
Summary
This issue is to explore the feasibility and potential of running the CI of all downstream dependencies in our codebase each time an upstream dependency has a PR open.
The value being to reduce the number of cases where we need to revert changes because they introduce breaking changes or are simply too hard to migrate, so a more progressive approach needs to be taken.
Examples
Motivation
No response
Search keywords: -