Package
lage
Describe the bug
When using --since, if you change a file that isn't in a package (e.g. README.md or CHANGELOG.md) and you are using --since to avoid rebuiling unaffected packages, it considers all packages as affected by that change.
To Reproduce
- Have a monorepo setup with some different packages that don't all depend on on another
- Have a file at the monorepo root (e.g. README.md)
- Edit the file at the monorepo root and a file in a package that not all the packages depend on
- Run
lage build --since origin/HEAD or similar to try and only build packages affected by the change
- Notice whether it only builds affected packages or builds ALL packages.
Expected behavior
If I use --since then only the dependsOn, inputs, and so on as configured in lage, plus its dependency graph detection from yarn.lock should be used to figure out the affected packages. Changes to documention, build scripts, that have nothing to do with the code being built should not cause a rebuild.
Environment/Troubleshooting
Package
lage
Describe the bug
When using
--since, if you change a file that isn't in a package (e.g. README.md or CHANGELOG.md) and you are using--sinceto avoid rebuiling unaffected packages, it considers all packages as affected by that change.To Reproduce
lage build --since origin/HEADor similar to try and only build packages affected by the changeExpected behavior
If I use
--sincethen only thedependsOn,inputs, and so on as configured inlage, plus its dependency graph detection fromyarn.lockshould be used to figure out the affected packages. Changes to documention, build scripts, that have nothing to do with the code being built should not cause a rebuild.Environment/Troubleshooting