From 2b906f652f9f12acc6ce83fae7c81c1e7386153b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Luk=C3=A1=C5=A1=20Matta?= Date: Mon, 6 Aug 2018 19:04:13 +0200 Subject: [PATCH] docs: fix typo (#25331) PR Close #25331 --- docs/BAZEL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/BAZEL.md b/docs/BAZEL.md index db4872ea53..4e129f28cb 100644 --- a/docs/BAZEL.md +++ b/docs/BAZEL.md @@ -153,7 +153,7 @@ Note that Bazel has a `--stamp` argument to `bazel build`, but this has no effec Bazel supports fetching action results from a cache, allowing a clean build to pick up artifacts from prior builds. This makes builds incremental, even on CI. It works because Bazel assigns a content-based hash to all action inputs, which is used as the cache key for the action outputs. -Thanks the the hermeticity property, we can skip executing an action if the inputs hash is already present in the cache. +Thanks to the hermeticity property, we can skip executing an action if the inputs hash is already present in the cache. Of course, non-hermeticity in an action can cause problems. At worst, you can fetch a broken artifact from the cache, making your build non-reproducible.