From aed058218be101a91d9624ba8eee17b8bd5f4b7f Mon Sep 17 00:00:00 2001 From: Laura Porta Date: Fri, 20 Oct 2023 14:27:11 +0100 Subject: [PATCH] Update docs/source/blog/intro_to_linting_and_ci.md Co-authored-by: Adam Tyson --- docs/source/blog/intro_to_linting_and_ci.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/blog/intro_to_linting_and_ci.md b/docs/source/blog/intro_to_linting_and_ci.md index b3a9b85..242c259 100644 --- a/docs/source/blog/intro_to_linting_and_ci.md +++ b/docs/source/blog/intro_to_linting_and_ci.md @@ -21,7 +21,7 @@ If you've ever followed a complex recipe, you'll understand the need for careful CI stands for Continuous Integration. Think of it as a kitchen assistant who keeps tasting the soup at every stage, ensuring it's always delicious. ### How does CI work? -CI is a process that **runs** automatically every time you make a change to your code. It checks that your code is working as expected, and alerts you if there are any problems. Every time you push a change to your codebase on GitHub, CI (your cooking assistant) can install your package, run your tests, and check your code for errors as if it were a user interacting with your software. +CI is a process that **runs** automatically every time you make a change to your code. It checks that your code is working as expected, and alerts you if there are any problems. Every time you push a change to your codebase on GitHub, CI (your cooking assistant) can install your package, test it, and check your code for errors as if it were a user interacting with your software. ### If I don't use CI, what could go wrong? Imagine baking a cake. If you don't taste-test as you go, you might end up with a salty dessert. Without CI, small errors in code can create big problems later.