We have a user that’s using LakeFS to introduce
code and data versioning as part of their assets in Dagster. Then, on
branch deployment, a new LakeFS reference is created, and is used in the branch deployment environment. By comparing the versioning of the assets from the branch deployment to that of production, the Dagster framework can then tell which assets should be materialized and tested in the LakeFS branch, before merging the new code to production.