◊(Local Yarn Code "Artifact [d9e10ede]")

Artifact d9e10ede7db9340501fb0cca842fbc7268de1447412bf6e79b2bc98d138f5044:

Wiki page [How to Use This Repo] by joel on 2018-08-11 13:56:35.
D 2018-08-11T13:56:35.508
L How\sto\sUse\sThis\sRepo
P 2925d37f9a7582f25a6ed1210d3bfbfe1ef8563c4d42e34735db00bc475f986e
U joel
W 2903
<h1>How to use this repo</h1>

You can “use” this repo by clicking around and reading code, wiki pages,&nbsp;etc.

But for those who have an account with the right permissions, it can also be used to check out a version-controlled copy of the code. 

I’m not yet giving out such accounts, not until the whole project is live. But, for the curious, this is how it would work if you had one:

<ol>
<li>If you don’t already have it, <a href="http://fossil-scm.org/index.html/uv/download.html">download</a> the Fossil executable and put it on your&nbsp;<code>$PATH</code></li>
<li>Clone this repository:
<pre><code><b>&gt;</b> fossil [https://fossil-scm.org/index.html/help?cmd=clone|clone] -u https://<i>user</i>:<i>password</i>@thelocalyarn.com/cgi-bin/yarncode yarn.fossil</code></pre></li>
<li>You might as well set autosync to <tt>0</tt> (off) or to <tt>pullonly</tt>. (See below for more info about&nbsp;why):
<pre><code><b>&gt;</b> fossil settings [https://fossil-scm.org/index.html/help?cmd=autosync|autosync] 0</code></pre></li>
<li>“Check out” the latest version of the source code into your current&nbsp;directory:
<pre><code><b>&gt;</b> fossil [https://fossil-scm.org/index.html/help?cmd=open|open] myclone.fossil</code></pre></li>
<li>Fiddle with the source code as you see fit. Read [http://fossil-scm.org/index.html/doc/trunk/www/quickstart.wiki|Fossil Quick Start].</li>
<li>You can also open your own local copy of the web&nbsp;UI:
<pre><code><b>&gt;</b> fossil ui</code></pre></li>
<li>To get the latest version of the&nbsp;code:
<pre><code><b>&gt;</b> fossil pull</code></pre></li>
</ol>

<h2>Some tips for Git users</h2>

  *  If you’re wondering why I’m using Fossil instead of Git, read [Why Fossil?]
  *  Fossil has <code>autosync</code> on by default, which means it will sync with the remote repo on every commit. But since you likely won’t have “push” privileges on my repo, it will fail. Turning autosync off will prevent you from having to see it try and fail every time you make a commit.
  *  There is no “staging” step in Fossil. Doing <a href="http://fossil-scm.org/index.html/help?cmd=commit"><code>fossil commit</code></a> immediately commits all changes in all tracked files into the repository. If you need to, you can specify which file or files you want to be included in the&nbsp;commit.
  *  There is no selective “patch committing” in Fossil (i.e., <code>git add -p</code> in Git), reportedly because it facilitates check-ins of untested code. So, if you’re in the habit of making unrelated edits to code…[https://youtu.be/Ow0lr63y4Mw?t=2m7s|stop it!]
  *  There is currently no “pull request” functionality in Fossil; users either have commit privileges or they don’t. This is fine for me since I am not interested in pull requests. If you would like to propose a change you can email me a patch.
Z 9e2d9dd8091882752249953d06d73420