From 29ccdd3087cbb9d5aa5d59740f43dbe3b9297c73 Mon Sep 17 00:00:00 2001 From: Hinton Date: Tue, 24 Oct 2023 19:04:39 +0200 Subject: [PATCH] Fix headers --- docs/contributing/dependencies/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/contributing/dependencies/index.md b/docs/contributing/dependencies/index.md index 55409af3..f25e57d4 100644 --- a/docs/contributing/dependencies/index.md +++ b/docs/contributing/dependencies/index.md @@ -55,7 +55,7 @@ version. Renovate has seen a **74%** test success rate across Renovate managed r a low confidence in the change. For more details read [Renovate documentation about Merge Confidence](https://docs.renovatebot.com/merge-confidence/). -## Review +### Review A typical dependency workflow involves the following steps: @@ -80,13 +80,13 @@ The handover between developers and QA will be a Jira ticket. The ticket should dependency, any relevant release notes for sections to test, and some testing notes on affected areas. -## QA Testing +### QA Testing While developers are responsible for writing a jira ticket with testing notes, the QA engineer should practice due diligence by also considering the impact of the dependency change and if needed discuss with the engineer about potentially increasing or decreasing the scope of testing. -## Reverting +### Reverting In the event QA finds a regression, the developer is responsible for assessing the impact and either immediately revert the update, or resolve the regression in a new PR.