infra(netlify): diff to next

[ST-DDT]

Currently, if you merge next into a PR, a build preview is created, even if the PR itself does not change anything docs related.

The new check uses next as a comparison base and uses a common ancestor comparison.
E.g. any changes on next in the meantime are ignored.

git diff next...some-branch vs git diff next some-branch

Unfortunately, this will refresh the preview for all commits in a PR that changes docs, not just those that affect the docs.

So more build-minutes spend on PRs that would change the docs. And no more build-minutes spend on PRs that don't change the docs.

[netlify]

✅ Deploy Preview for fakerjs ready!

Name	Link
🔨 Latest commit	5f96368
🔍 Latest deploy log	https://app.netlify.com/sites/fakerjs/deploys/65f855d81a74960009532248
😎 Deploy Preview	https://deploy-preview-2755.fakerjs.dev
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.93%. Comparing base (6dee178) to head (5f96368).

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #2755      +/-   ##
==========================================
- Coverage   99.93%   99.93%   -0.01%     
==========================================
  Files        2958     2958              
  Lines      213715   213715              
  Branches      950      948       -2     
==========================================
- Hits       213583   213568      -15     
- Misses        132      143      +11     
- Partials        0        4       +4     

see 6 files with indirect coverage changes

[ST-DDT]

Alternatively, we could check for a /^docs/ (+feat+refactor?) commit name.

Or maybe even a specific (empty) enable netlify commit.

I would have to check that though if it does strange things with update to next though.

[xDivisionByZerox]

Alternatively, we could check for a /^docs/ (+feat+refactor?) commit name.

Or maybe even a specific (empty) enable netlify commit.

I would have to check that though if it does strange things with update to next though.

KISS. If we need to change the process again, we can have a look if it's required.