From 0fed05a7522797f256086d0b042fc0702cec6a4e Mon Sep 17 00:00:00 2001 From: Mike McQuaid Date: Tue, 24 Aug 2021 13:56:10 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Rylan Polster --- docs/Homebrew-brew-Maintainer-Guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Homebrew-brew-Maintainer-Guide.md b/docs/Homebrew-brew-Maintainer-Guide.md index 0abaeed845..080304056c 100644 --- a/docs/Homebrew-brew-Maintainer-Guide.md +++ b/docs/Homebrew-brew-Maintainer-Guide.md @@ -99,13 +99,13 @@ reports are available to Homebrew maintainers on [buildpulse.io](https://buildpu summaries are published to [`#buildpulse-health`](https://machomebrew.slack.com/archives/C0268BSJBJ8) in Slack. BuildPulse can be used as a guide to identify which flaky tests are causing the most disruption to the CI suite. To make -the biggest improvements to the reliability of the build, we can focus on the most disruptive flaky tests first (i.e., +the biggest improvements to the reliability of the build, we can focus on the most disruptive flaky tests first (i.e. the tests causing the most intermittent failures). To help find the root cause for a particular flaky test, buildpulse.io provides links to the most recent CI job and commit where the test failed and then passed with no change to the underlying code. You may want to check out the code at that commit to attempt to reproduce the failure locally. You can also see the list of recent failures on -buildpulse.io to determine if the test always fails the same way. +[buildpulse.io](https://buildpulse.io) to determine if the test always fails the same way. ## Manpages and shell completions