ok/jj
1
0
Fork 0
forked from mirrors/jj
Code Pull requests Activity

Deployed 5bd7588 to prerelease with MkDocs 1.6.0 and mike 2.1.1

Browse source
This commit is contained in:
jj-docs[bot] 2024-09-16 23:45:08 +00:00
parent 0b7cd9d1cc
commit 1d368dcf2a
2 changed files with 16 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
prerelease/branches/index.html Normal file
View file

@ -0,0 +1,15 @@
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Redirecting...</title>
<link rel="canonical" href="../bookmarks/">
<meta name="robots" content="noindex">
<script>var anchor=window.location.hash.substr(1);location.href="../bookmarks/"+(anchor?"#"+anchor:"")</script>
<meta http-equiv="refresh" content="0; url=../bookmarks/">
</head>
<body>
Redirecting...
</body>
</html>

2
prerelease/contributing/index.html
View file

@ -1789,7 +1789,7 @@ test and document.</p>
<p>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
<a href="www.conventionalcommits.org/en/v1.0.0/">conventional commits</a>. This means if
<a href="https://www.conventionalcommits.org/en/v1.0.0/">conventional commits</a>. This means if
you modified a command in the CLI, use its name as the topic, e.g
<code>next/prev: &lt;your-modification&gt;</code> or <code>conflicts: &lt;your-modification&gt;</code>. We don't
currently have a specific guidelines on what to write in the topic field, but