📚 The `defaultBranch` feature for `vcs` should specify where it is in effect

[jakeleventhal]

Documentation URL

https://biomejs.dev/guides/integrate-in-vcs/#process-only-changed-files

Description

To me it doesn't make sense that you would want this functionality for the linter, only the formatter. In many cases if you edit file A, it may break lint rules in file B that imports A.

Expectations

The documentation and rule should update to either only apply to the formatter, or know which files downstream would also need to be checked.

Code of Conduct

• I agree to follow Biome's Code of Conduct

[jakeleventhal]

The same applies to https://biomejs.dev/guides/integrate-in-vcs/#process-only-staged-files

[ematipico]

I don't understand your example and how it's related to the VCS functionality - maybe try to add more particulars to your description (e.g. concrete examples/rules).

[jakeleventhal]

Sorry, here is what I mean:

// file1.ts
- const Something = ...
+ type Something = ...

export { Something }

// file2.ts
import { Something } from './file1';
...

If you only have diff in file1, perhaps some downstream file2 will have a TS-related lint error that is not actually a true TS error. The above example is a bit contrived but the point remains.