From a44f3f30671d85380a48b39df84fb5b4851232fd Mon Sep 17 00:00:00 2001
From: Tim Neutkens <tim@timneutkens.nl>
Date: Fri, 24 May 2024 13:18:05 +0200
Subject: [PATCH] Update contributing guide to mention snapshot test updating
 (#8185)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

### Description

Had to ask this info from the rest of the team, ensures it's documented.

<!--
  ✍️ Write a short summary of your work.
  If necessary, include relevant screenshots.
-->

### Testing Instructions

<!--
  Give a quick description of steps to test your changes.
-->
---
 CONTRIBUTING.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ea423f2217251..602443586d05f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -6,6 +6,7 @@ Thanks for your interest in contributing to Turbo!
 
 - [Contributing to Turbo](#contributing-to-turbo)
   - [General Dependencies](#general-dependencies)
+    - [Linux Dependencies](#linux-dependencies)
   - [Contributing to Turborepo](#contributing-to-turborepo)
     - [Building Turborepo](#building-turborepo)
     - [TLS Implementation](#tls-implementation)
@@ -290,6 +291,14 @@ You can also create a little demo app and run
 cargo run -p node-file-trace -- print demo/index.js
 ```
 
+Updating snapshot tests:
+
+In case of changes that involve updating snapshots you can use the `UPDATE=1` environment variable.
+
+```
+UPDATE=1 cargo nextest run
+```
+
 ### Profiling Turbopack
 
 See [the profiling docs for Turbopack](https://turbo.build/pack/docs/advanced/profiling) for details.