From ea806bfa732296bafdef4abac55169b3a62e7229 Mon Sep 17 00:00:00 2001 From: Humble Chirammal Date: Fri, 11 Nov 2022 14:53:31 +0530 Subject: [PATCH] docs: update/correct development guide the pre-commit version in the developement guide was too outdated which has been updated and this commit also addressed a typo. Signed-off-by: Humble Chirammal --- docs/development-guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/development-guide.md b/docs/development-guide.md index cadefa292..28d1130c8 100644 --- a/docs/development-guide.md +++ b/docs/development-guide.md @@ -46,7 +46,7 @@ it is **highly** encouraged to: * Set up a pre-commit hook to catch issues locally. ```console - pip install pre-commit==2.5.1 + pip install pre-commit pre-commit install ``` @@ -338,7 +338,7 @@ fresh PRs, rebase of PRs and force pushing changes to existing PRs. In case of failed we already documented steps to manually [retrigger](#retriggering-the-ci-jobs) the CI jobs. Sometime the tests might be flaky which required manually retriggering always. We have newly added a github -action which runs periodically to retest the failed PR's. Below are the cretia +action which runs periodically to retest the failed PR's. Below are the criteria for auto retesting the failed PR. * Analyze the logs and make sure its a flaky test.