Deployed 4d19a0a to prerelease with MkDocs 1.6.1 and mike 2.1.3

This commit is contained in:
jj-docs[bot] 2024-11-23 07:06:05 +00:00
parent 9515188ea9
commit 28fdfdced8
2 changed files with 2 additions and 2 deletions

View File

@ -6424,7 +6424,7 @@ does not match the <code>jj help</code> output exactly.</p>
</li> </li>
<li> <li>
<p><code>--ignore-working-copy</code> — Don't snapshot the working copy, and don't update it</p> <p><code>--ignore-working-copy</code> — Don't snapshot the working copy, and don't update it</p>
<p>By default, Jujutsu snapshots the working copy at the beginning of every command. The working copy is also updated at the end of the command, if the command modified the working-copy commit (<code>@</code>). If you want to avoid snapshotting the working copy and instead see a possibly stale working copy commit, you can use <code>--ignore-working-copy</code>. This may be useful e.g. in a command prompt, especially if you have another process that commits the working copy.</p> <p>By default, Jujutsu snapshots the working copy at the beginning of every command. The working copy is also updated at the end of the command, if the command modified the working-copy commit (<code>@</code>). If you want to avoid snapshotting the working copy and instead see a possibly stale working-copy commit, you can use <code>--ignore-working-copy</code>. This may be useful e.g. in a command prompt, especially if you have another process that commits the working copy.</p>
<p>Loading the repository at a specific operation with <code>--at-operation</code> implies <code>--ignore-working-copy</code>.</p> <p>Loading the repository at a specific operation with <code>--at-operation</code> implies <code>--ignore-working-copy</code>.</p>
</li> </li>
<li> <li>

File diff suppressed because one or more lines are too long