Skip to content

Commit

Permalink
Deployed 0690922 to prerelease with MkDocs 1.6.0 and mike 2.1.1
Browse files Browse the repository at this point in the history
  • Loading branch information
jj-docs[bot] committed Jul 11, 2024
1 parent 3b059c3 commit f8629cb
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 2 deletions.
5 changes: 4 additions & 1 deletion prerelease/FAQ/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1665,7 +1665,10 @@ <h3 id="how-can-i-keep-my-scratch-files-in-the-repository">How can I keep my scr
files you want to keep around to match the pattern.</p>
<p>If <code>$EDITOR</code> integration is important, something like <code>scratchpad.*</code> may be more
helpful, as you can keep the filename extension intact (it
matches <code>scratchpad.md</code>, <code>scratchpad.rs</code> and more).</p>
matches <code>scratchpad.md</code>, <code>scratchpad.rs</code> and more). Another option is to add a
directory to the global <code>.gitignore</code> which then stores all your temporary files
and notes. For example, you could add <code>scratch/</code> to <code>~/.git/ignore</code> and then
store arbitrary files in <code>&lt;your-git-repo&gt;/scratch/</code>.</p>
<p>You can find more details on <code>gitignore</code> files <a href="https://git-scm.com/docs/gitignore">here</a>.</p>
<h3 id="how-can-i-keep-local-changes-around-but-not-use-them-for-pull-requests">How can I keep local changes around, but not use them for Pull Requests?<a class="headerlink" href="#how-can-i-keep-local-changes-around-but-not-use-them-for-pull-requests" title="Permanent link">&para;</a></h3>
<p>In general, you should separate out the changes to their own commit (using
Expand Down
2 changes: 1 addition & 1 deletion prerelease/search/search_index.json

Large diffs are not rendered by default.

0 comments on commit f8629cb

Please sign in to comment.