drone build Wed Oct 14 08:29:48 PDT 2026
This commit is contained in:
1 parent
0395f8d660
commit
6acd946a71
319 files changed
+3628
-3653
No files matched your search
+15
-14
@@ -2111,6 +2111,7 @@ switch (currentThemeValue) {
|
||||
</aside>
|
||||
|
||||
<p>alrighty, this one's a real doozy. Strap in.</p>
|
||||
<p>and as always, if you find an error or have feedback, please <a href="/contact">let me know</a>.</p>
|
||||
<h2 id="versioning">versioning</h2>
|
||||
<p>have you ever tried to revert to a previous version of a document in MS Office or Google Docs and found that your revision history is cluttered with small changes that by all rights should be grouped into one set of edits, but they aren't, and it's tedious to pick through all the versions?</p>
|
||||
<p>or, more uniquely and/or uncommonly:</p>
|
||||
@@ -2123,7 +2124,7 @@ switch (currentThemeValue) {
|
||||
<p>I started writing this to help a friend. She's getting started with a website, and we're using the static site generator <a href="https://www.11ty.dev/" target="_blank" rel="external">11ty</a> as she wants to have a lot of easy-to-write posts. She needs a single-user workflow that allows her to publish her website without hosting it herself, and that's the use case where this was born.</p>
|
||||
<p>this walkthrough is best suited for people who want to use <code>git</code> in single-person projects, or perhaps with one or two other close collaborators. There's quite a few topics it doesn't cover that are vitally important in large collaborative projects, such as <strong>branching</strong> and <strong>merging</strong>.</p>
|
||||
<p>this walkthrough also focuses on the "happy path," without much discussion of troubleshooting. I may write more on the topic in the future, but we're already over <em>4,500 words</em>, so we're calling it a day.</p>
|
||||
<p>finally, I wrote this walkthrough primarily with knowledge from using <strong>WSL</strong> [more on this later] on <strong>Windows</strong> and with <strong>Zed</strong> as my text editor. While I've tried to cover my bases with other OSes and options, there's a solid chance I'm missing things!</p>
|
||||
<p>finally, I wrote this walkthrough primarily with knowledge from using <strong>WSL</strong> [more on this later] on <strong>Windows</strong> and with <strong>Zed</strong> as my text editor, and I've since lightly reviewed from <strong>Linux Mint</strong> with <strong>Gram</strong> as my text editor. While I've tried to cover my bases with other OSes and options, there's a solid chance I'm missing things!</p>
|
||||
<p>that all said, let's get (git?) into it!</p>
|
||||
<h2 id="what-is-git%3F">what is <code>git</code>?</h2>
|
||||
<p><code>git</code> is a <em>version control system</em>. We can use it to track changes we make to a set of files.</p>
|
||||
@@ -2143,14 +2144,14 @@ switch (currentThemeValue) {
|
||||
<h3 id="where-can-i-use-the-git-cli%3F">where can I use the <code>git</code> CLI?</h3>
|
||||
<p>if you want to use the <code>git</code> CLI, you'll need a terminal. You've got a couple options here:</p>
|
||||
<ul>
|
||||
<li>on Linux or Mac, you should have one built in! This is the easy path, congrats :) Even better, <code>git</code> generally ships with these systems, so there's no installation required. Search for an application called 'Terminal' or similar
|
||||
<li>on Linux or Mac, you should have one built in! This is the easy path, congrats :) Even better, <code>git</code> generally ships with these systems (or is a one-liner install such as <code>apt install git</code>). Search for an application called 'Terminal' or similar
|
||||
<ul>
|
||||
<li>note that I don't have a Mac and have never used one. I can't guarantee that everything operates the same over there - there may be discrepancies I don't know about</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>on Windows, there's two options
|
||||
<ul>
|
||||
<li><a href="https://gitforwindows.org/" target="_blank" rel="external"><code>git</code> for Windows</a> packages a Linux-like terminal with a <code>git</code> GUI. This may be slightly friendlier for people who aren't at all familiar with Linux. If choosing <code>git</code> for Windows, <a href="#git-for-windows">see my installation instructions below</a></li>
|
||||
<li><a href="https://gitforwindows.org/" target="_blank" rel="external"><code>git</code> for Windows</a> packages a Linux-like terminal with a <code>git</code> GUI. This is probably the friendlier option to get started with. If choosing <code>git</code> for Windows, <a href="#git-for-windows">see my installation instructions below</a></li>
|
||||
<li>I use <a href="https://learn.microsoft.com/en-us/windows/wsl/install" target="_blank" rel="external">Windows Subsystem for Linux, or WSL</a>, which gives you a Linux distribution within Windows. It's pretty smooth sailing at this point, but there's some idiosyncracies to conquer - like the fact that your <em>Windows</em> files and your <em>Linux</em> files are stored in different places. If choosing WSL, <a href="#wsl">see my usage notes below</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -2170,7 +2171,7 @@ switch (currentThemeValue) {
|
||||
<p>while <em>installing</em> WSL is a single command, here's a couple notes about getting started once <em>inside</em> WSL:</p>
|
||||
<ul>
|
||||
<li>don't be concerned that you can't see anything when you type or paste your password! Since it's sensitive information, this is intentional. You'll notice this pattern a couple of times while following this walkthrough</li>
|
||||
<li><code>Ctrl+C</code> and <code>Ctrl+V</code> won't work like they do on Windows. If you want to copy/paste, right-click (there won't be a context menu, it'll just happen)</li>
|
||||
<li><code>Ctrl+C</code> and <code>Ctrl+V</code> won't work like they do on Windows. If you want to copy/paste, use <code>Shift+Ctrl+C</code> and <code>Shift+Ctrl+V</code></li>
|
||||
<li>if you're downloading a text editor like the ones mentioned above, you'll still follow the <em>Windows</em> instructions</li>
|
||||
</ul>
|
||||
<p>you'll also need to be careful of a few things regarding text editors to make them work with WSL:</p>
|
||||
@@ -2488,43 +2489,43 @@ codeberg https://codeberg.org/inherentlee/git-intro.git (push)</code></pre>
|
||||
<ol id="postlist">
|
||||
|
||||
<li class="post">
|
||||
<a class="postlink" href="/visual-site-builders-and-accessibility/">
|
||||
<h2 data-ha-exclude="">visual site builders and accessibility </h2>
|
||||
<a class="postlink" href="/redirections/">
|
||||
<h2 data-ha-exclude="">redirections </h2>
|
||||
|
||||
<ul class="postlist-tags">
|
||||
|
||||
<li>software</li>
|
||||
|
||||
</ul>
|
||||
<img src="/img/roses.jpg" alt="Image unrelated to post. Two peach-colored roses, the farther away one a bit out of focus." loading="lazy" decoding="async" width="1000" height="666">
|
||||
<img src="/img/angle-brackets-uwu.jpg" alt="Ascii art of an emoticon with pinched eyes and a small mouth made with two angle brackets." loading="lazy" decoding="async" width="1000" height="316">
|
||||
|
||||
</a>
|
||||
</li>
|
||||
|
||||
<li class="post">
|
||||
<a class="postlink" href="/framer-accessibility/">
|
||||
<h2 data-ha-exclude="">framer accessibility </h2>
|
||||
<a class="postlink" href="/screen-reader-optimizations/">
|
||||
<h2 data-ha-exclude="">screen reader optimizations </h2>
|
||||
|
||||
<ul class="postlist-tags">
|
||||
|
||||
<li>software</li>
|
||||
|
||||
</ul>
|
||||
<img src="/img/feather.jpg" alt="Image unrelated to post. A very frail and wispy feather with variegated white and brown markings on top of pine-needle-covered ground." loading="lazy" decoding="async" width="1000" height="666">
|
||||
<img src="/img/crow.jpg" alt="Image unrelated to post. A crow poses on driftwood against a whitish sky." loading="lazy" decoding="async" width="1000" height="666">
|
||||
|
||||
</a>
|
||||
</li>
|
||||
|
||||
<li class="post">
|
||||
<a class="postlink" href="/accessible-image-modals/">
|
||||
<h2 data-ha-exclude="">accessible image modals </h2>
|
||||
<a class="postlink" href="/domain-and-site-setup/">
|
||||
<h2 data-ha-exclude="">domain and site setup </h2>
|
||||
|
||||
<ul class="postlist-tags">
|
||||
|
||||
<li>software</li>
|
||||
|
||||
</ul>
|
||||
<img src="/img/snacking-seagull.jpg" alt="Image unrelated to post. A seagull floating in the water with a starfish hanging out of eir mouth." loading="lazy" decoding="async" width="1000" height="666">
|
||||
<img src="/img/crinkly-mushrooms.jpg" alt="Picture unrelated to post. Some crinkly brown-orange mushrooms in vibrant green grass." loading="lazy" decoding="async" width="1000" height="750">
|
||||
|
||||
</a>
|
||||
</li>
|
||||
@@ -2581,6 +2582,6 @@ codeberg https://codeberg.org/inherentlee/git-intro.git (push)</code></pre>
|
||||
</footer>
|
||||
|
||||
|
||||
<!-- This page `/an-intro-to-git/` was built on 2026-10-13T15:32:13.264Z -->
|
||||
<!-- This page `/an-intro-to-git/` was built on 2026-10-14T15:29:14.393Z -->
|
||||
</body>
|
||||
</html>
|
||||
Reference in new issue
Block a user