From 45c249760beaea2194f2917a43055f7d7ade0fc2 Mon Sep 17 00:00:00 2001 From: Kevin Finn Date: Thu, 28 Aug 2025 17:56:51 -0400 Subject: [PATCH] Fix outdated documentation for UpdateSourceFiles cb3fe1711b7e6c068da01a25aee412fcdd07d68e updated the example source code to use `UpdateSourceFiles` instead of `WriteFiles`, but failed to update the English description on the page. This updates the English description. --- content/en-US/learn/build-system.smd | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/content/en-US/learn/build-system.smd b/content/en-US/learn/build-system.smd index 0b35b559f..6811ded27 100644 --- a/content/en-US/learn/build-system.smd +++ b/content/en-US/learn/build-system.smd @@ -415,11 +415,7 @@ zig-out/ It is uncommon, but sometimes the case that a project commits generated files into version control. This can be useful when the generated files are seldomly updated and have burdensome system dependencies for the update process, but *only* during the -update process. - -For this, **WriteFiles** provides a way to accomplish this task. This is a feature that -[will be extracted from WriteFiles into its own Build Step](https://github.com/ziglang/zig/issues/14944) -in a future Zig version. +update process. **UpdateSourceFiles** provides a way to accomplish this task. Be careful with this functionality; it should not be used during the normal build process, but as a utility run by a developer with intention to update