From 4483d255066a9c6200c4d297a778e5af02b0f248 Mon Sep 17 00:00:00 2001 From: Daniel McCloy Date: Sun, 11 May 2025 17:38:16 -0700 Subject: [PATCH] WIP --- content/how-tos/ci-logs.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 content/how-tos/ci-logs.md diff --git a/content/how-tos/ci-logs.md b/content/how-tos/ci-logs.md new file mode 100644 index 0000000..4984a61 --- /dev/null +++ b/content/how-tos/ci-logs.md @@ -0,0 +1,20 @@ +--- +title: "How do I access CI logs?" +--- + +{{< admonition warning >}} +This is a draft document. +{{< /admonition >}} + +Most packages use _continuous integration_ (CIs) to ensure that new code contributions don't break existing functionality. +CIs do things like run code style checks, run unit tests on different operating systems or different dependency versions, and build documentation websites. +Frequently, when you contribute bugfixes, new features, or documentation changes to a packages, one or more of the CIs will fail. +Below, we show how to figure out _why_ they failed, and what to do to fix them. + + + + + + + +