From 1d368dcf2aeb8ee85c74a1d560a3d50163e5004a Mon Sep 17 00:00:00 2001 From: "jj-docs[bot]" Date: Mon, 16 Sep 2024 23:45:08 +0000 Subject: [PATCH] Deployed 5bd7588 to prerelease with MkDocs 1.6.0 and mike 2.1.1 --- prerelease/branches/index.html | 15 +++++++++++++++ prerelease/contributing/index.html | 2 +- 2 files changed, 16 insertions(+), 1 deletion(-) create mode 100644 prerelease/branches/index.html diff --git a/prerelease/branches/index.html b/prerelease/branches/index.html new file mode 100644 index 000000000..e2afba1f8 --- /dev/null +++ b/prerelease/branches/index.html @@ -0,0 +1,15 @@ + + + + + + Redirecting... + + + + + + +Redirecting... + + diff --git a/prerelease/contributing/index.html b/prerelease/contributing/index.html index 3d6f35952..85d7d2abf 100644 --- a/prerelease/contributing/index.html +++ b/prerelease/contributing/index.html @@ -1789,7 +1789,7 @@ test and document.

The commit message should describe the changes in the commit; the PR description can even be empty, but feel free to include a personal message. We write commit messages in an affected component style and don't use -conventional commits. This means if +conventional commits. This means if you modified a command in the CLI, use its name as the topic, e.g next/prev: <your-modification> or conflicts: <your-modification>. We don't currently have a specific guidelines on what to write in the topic field, but