Skip to content

Snapshot-based content change assertion #420

@ovflowd

Description

@ovflowd

Enter your suggestions in details:

This would be an important feature to ensure that:

  1. We have baseline:
  • The baseline gets automatically updated on every time a new commit happens on nodejs/node via GHA
  • We can also get notified maybe if the baseline changes too much? Which could flag peerDep change issues or some massive content change upstream?
  1. On every PR it runs a CI that runs all generators and stores snapshots of them (same as happens on main` except that it doesn't override the baseline files)
  • It compares against the baseline and "cries"/fails if the content changed
  • This would allow us to verify easily and seamlessly if changes in PR are affecting content generation
  • The failure could be rendered as a git diff between these two files

cc @nodejs/web-infra

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions