diff --git a/404.html b/404.html
index 57b6e7b..07f759e 100644
--- a/404.html
+++ b/404.html
@@ -397,9 +397,9 @@ <h1>Page not found</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/404.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/404.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/CODE_OF_CONDUCT.html b/CODE_OF_CONDUCT.html
index 5f23831..5cfdb5c 100644
--- a/CODE_OF_CONDUCT.html
+++ b/CODE_OF_CONDUCT.html
@@ -415,9 +415,9 @@ <h1>Contributor Code of Conduct</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/CODE_OF_CONDUCT.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/CODE_OF_CONDUCT.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-11-18",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/LICENSE.html b/LICENSE.html
index 9eb273a..c64d971 100644
--- a/LICENSE.html
+++ b/LICENSE.html
@@ -463,9 +463,9 @@ <h1>Licenses</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/LICENSE.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/LICENSE.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-11-18",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/advanced-git-commands.html b/advanced-git-commands.html
index f0920be..dc7b8b6 100644
--- a/advanced-git-commands.html
+++ b/advanced-git-commands.html
@@ -620,7 +620,7 @@ <h3 class="callout-title">Review Changes</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
 <div class="accordion-body">
 <p>On the command line, the Collaborator can use
 <code>git fetch origin main</code> to get the remote changes into the
@@ -1045,7 +1045,7 @@ <h3 class="callout-title">Conflicts on Non-textual files</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
 <div class="accordion-body">
 <p>Let’s try it. Suppose Alfredo takes a picture of its guacamole and
 calls it <code>guacamole.jpg</code>.</p>
@@ -1263,7 +1263,7 @@ <h3 class="callout-title">A Typical Work Session</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution3" aria-expanded="false" aria-controls="collapseSolution3">
   <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 </button>
-<div id="collapseSolution3" class="accordion-collapse collapse" aria-labelledby="headingSolution3" data-bs-parent="#accordionSolution3">
+<div id="collapseSolution3" class="accordion-collapse collapse" data-bs-parent="#accordionSolution3" aria-labelledby="headingSolution3">
 <div class="accordion-body">
 <table class="table"><colgroup><col width="6%"><col width="34%"><col width="59%"></colgroup><thead><tr class="header"><th>order</th>
 <th>action . . . . . .</th>
@@ -1384,9 +1384,9 @@ <h3 class="callout-title">Key Points</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/advanced-git-commands.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/advanced-git-commands.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-12-12",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/aio.html b/aio.html
index e7beb74..2731183 100644
--- a/aio.html
+++ b/aio.html
@@ -3297,7 +3297,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-gitlab"><p>Content from <a href="gitlab.html">GitLab</a></p>
 <hr>
-<p>Last updated on 2024-12-17 |
+<p>Last updated on 2024-12-19 |
 
         <a href="https://github.com/QuTech-Delft/prosoftdev-research/edit/main/episodes/gitlab.Rmd" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <div class="text-end">
@@ -3558,6 +3558,345 @@ <h3 id="archiving-a-project">Archiving a Project<a class="anchor" aria-label="an
 <p>At the bottom of the page is also a section for deleting a project,
 in case you ever think that is the right thing to do.</p>
 </div>
+</section><section><h2 class="section-heading" id="connecting-gitlab-projects-with-local-git-repositories">Connecting GitLab Projects with Local Git Repositories<a class="anchor" aria-label="anchor" href="#connecting-gitlab-projects-with-local-git-repositories"></a>
+</h2>
+<hr class="half-width">
+<p>Remember from an earlier lesson that we have created a local Git
+repository that looked like this:</p>
+<figure><img src="fig/git-staging-area.svg" alt="Local repository with staging area" class="figure mx-auto d-block"></figure><p>Now we want to have a GitLab project that will be coupled with this
+local Git repo. The first step here is to follow the steps described in
+the previous section, and create a new GitLab project called ‘recipes’.
+Initially the Git repo for this GitLab project will be empty, as shown
+in the diagram below:</p>
+<figure><img src="fig/git-freshly-made-gitlab-repo.svg" alt="The local and remote Git repos" class="figure mx-auto d-block"></figure><div class="section level3">
+<h3 id="connecting-the-local-to-remote-repository">Connecting the local to remote repository<a class="anchor" aria-label="anchor" href="#connecting-the-local-to-remote-repository"></a>
+</h3>
+<p>Now we connect the two repositories. We do this by making the GitHub
+repository a <a href="reference.html#remote">remote</a> for the local
+repository. Go to the home page of the repository on GitLab, click on
+the blue <code>Code</code> button, and copy the string below the
+<code>Clone with SSH</code></p>
+<figure><img src="fig/gitlab_ssh_repo.jpg" alt="Accessing a GitLab repo via SSH" class="figure mx-auto d-block"></figure><div id="https-vs.-ssh" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="https-vs.-ssh" class="callout-inner">
+<h3 class="callout-title">HTTPS vs. SSH</h3>
+<div class="callout-content">
+<p>We use SSH here because, while it requires some additional
+configuration, it is a security protocol widely used by many
+applications. The steps below describe SSH at a minimum level for
+GitLab.</p>
+</div>
+</div>
+</div>
+<p>With the <code>Clone with SSH</code> string you copied from the
+GitLab page, go into the local <code>recipes</code> repository, and run
+this command:</p>
+<div class="codewrapper sourceCode" id="cb1">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" tabindex="-1"></a><span class="ex">$</span> git remote add origin git@gitlab.tudelft.nl:alflin/recipes.git</span></code></pre>
+</div>
+<p>Make sure to use the URL for your repository rather than Alfredo’s:
+the only difference should be your username instead of
+<code>alflin</code>.</p>
+<p><code>origin</code> is a local name used to refer to the remote
+repository. It could be called anything, but <code>origin</code> is a
+convention that is often used by default in git and GitHub, so it’s
+helpful to stick with this unless there’s a reason not to.</p>
+<p>We can check that the command has worked by running
+<code>git remote -v</code>:</p>
+<div class="codewrapper sourceCode" id="cb2">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a><span class="ex">$</span> git remote <span class="at">-v</span></span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>origin   git@gitlab.tudelft.nl:alflin/recipes.git (fetch)
+origin   git@gitlab.tudelft.nl:alflin/recipes.git (push)</code></pre>
+</div>
+</div>
+<div class="section level3">
+<h3 id="ssh-background-and-setup">SSH Background and Setup<a class="anchor" aria-label="anchor" href="#ssh-background-and-setup"></a>
+</h3>
+<p>Before Alfredo can connect to a remote repository, he needs to set up
+a way for his computer to authenticate with GitLab so it knows it’s him
+trying to connect to his remote repository.</p>
+<p>We are going to set up the method that is commonly used by many
+different services to authenticate access on the command line. This
+method is called Secure Shell Protocol (SSH). SSH is a cryptographic
+network protocol that allows secure communication between computers
+using an otherwise insecure network.</p>
+<p>SSH uses what is called a key pair. This is two keys that work
+together to validate access. One key is publicly known and called the
+public key, and the other key called the private key is kept private.
+Very descriptive names.</p>
+<p>You can think of the public key as a padlock, and only you have the
+key (the private key) to open it. You use the public key where you want
+a secure method of communication, such as your GitHub account. You give
+this padlock, or public key, to GitLab and say “lock the communications
+to my account with this so that only computers that have my private key
+can unlock communications and send git commands as my GitHub
+account.”</p>
+<p>What we will do now is the minimum required to set up the SSH keys
+and add the public key to a GitLab account.</p>
+<p>The first thing we are going to do is check if this has already been
+done on the computer you’re on. Because generally speaking, this setup
+only needs to happen once and then you can forget about it.</p>
+<div id="keeping-your-keys-secure" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="keeping-your-keys-secure" class="callout-inner">
+<h3 class="callout-title">Keeping your keys secure</h3>
+<div class="callout-content">
+<p>You shouldn’t really forget about your SSH keys, since they keep your
+account secure. It’s good practice to audit your secure shell keys every
+so often. Especially if you are using multiple computers to access your
+account.</p>
+</div>
+</div>
+</div>
+<p>We will run the list command to check what key pairs already exist on
+your computer.</p>
+<div class="codewrapper sourceCode" id="cb4">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" tabindex="-1"></a><span class="ex">$</span> ls <span class="at">-al</span> ~/.ssh</span></code></pre>
+</div>
+<p>Your output is going to look a little different depending on whether
+or not SSH has ever been set up on the computer you are using.</p>
+<p>Alfredo has not set up SSH on his computer, so his output is</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>ls: cannot access '/c/Users/Alfredo/.ssh': No such file or directory</code></pre>
+</div>
+<p>If SSH has been set up on the computer you’re using, the public and
+private key pairs will be listed. The file names are either
+<code>id_ed25519</code>/<code>id_ed25519.pub</code> or
+<code>id_rsa</code>/<code>id_rsa.pub</code> depending on how the key
+pairs were set up. Since they don’t exist on Alfredo’s computer, he uses
+this command to create them.</p>
+<div class="section level5">
+<h5 id="create-an-ssh-key-pair">Create an SSH key pair<a class="anchor" aria-label="anchor" href="#create-an-ssh-key-pair"></a>
+</h5>
+<p>To create an SSH key pair Alfredo uses this command, where the
+<code>-t</code> option specifies which type of algorithm to use and
+<code>-C</code> attaches a comment to the key (here, Alfredo’s
+email):</p>
+<div class="codewrapper sourceCode" id="cb6">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" tabindex="-1"></a><span class="ex">$</span> ssh-keygen <span class="at">-t</span> ed25519 <span class="at">-C</span> <span class="st">"a.linguini@ratatouille.fr"</span></span></code></pre>
+</div>
+<p>If you are using a legacy system that doesn’t support the Ed25519
+algorithm, use:
+<code>$ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"</code></p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Generating public/private ed25519 key pair.
+Enter file in which to save the key (/c/Users/Alfredo/.ssh/id_ed25519):</code></pre>
+</div>
+<p>We want to use the default file, so just press <kbd>Enter</kbd>.</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Created directory '/c/Users/Alfredo/.ssh'.
+Enter passphrase (empty for no passphrase):</code></pre>
+</div>
+<p>Now, it is prompting Alfredo for a passphrase. Since he is using his
+kitchen’s laptop that other people sometimes have access to, he wants to
+create a passphrase. Be sure to use something memorable or save your
+passphrase somewhere, as there is no “reset my password” option. Note
+that, when typing a passphrase on a terminal, there won’t be any visual
+feedback of your typing. This is normal: your passphrase will be
+recorded even if you see nothing changing on your screen.</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Enter same passphrase again:</code></pre>
+</div>
+<p>After entering the same passphrase a second time, we receive the
+confirmation</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Your identification has been saved in /c/Users/Alfredo/.ssh/id_ed25519
+Your public key has been saved in /c/Users/Alfredo/.ssh/id_ed25519.pub
+The key fingerprint is:
+SHA256:SMSPIStNyA00KPxuYu94KpZgRAYjgt9g4BA4kFy3g1o a.linguini@ratatouille.fr
+The key's randomart image is:
++--[ED25519 256]--+
+|^B== o.          |
+|%*=.*.+          |
+|+=.E =.+         |
+| .=.+.o..        |
+|....  . S        |
+|.+ o             |
+|+ =              |
+|.o.o             |
+|oo+.             |
++----[SHA256]-----+</code></pre>
+</div>
+<p>The “identification” is actually the private key. You should never
+share it. The public key is appropriately named. The “key fingerprint”
+is a shorter version of a public key.</p>
+<p>Now that we have generated the SSH keys, we will find the SSH files
+when we check.</p>
+<div class="codewrapper sourceCode" id="cb11">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="fu">ls</span> <span class="at">-al</span> ~/.ssh</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>drwxr-xr-x 1 Alfredo   197121   0 Jul 16 14:48 ./
+drwxr-xr-x 1 Alfredo   197121   0 Jul 16 14:48 ../
+-rw-r--r-- 1 Alfredo   197121 419 Jul 16 14:48 id_ed25519
+-rw-r--r-- 1 Alfredo   197121 106 Jul 16 14:48 id_ed25519.pub</code></pre>
+</div>
+</div>
+<div class="section level5">
+<h5 id="copy-the-public-key-to-github">Copy the public key to GitHub<a class="anchor" aria-label="anchor" href="#copy-the-public-key-to-github"></a>
+</h5>
+<p>Now we have a SSH key pair and we can run this command to check if
+GitHub can read our authentication.</p>
+<div class="codewrapper sourceCode" id="cb13">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="fu">ssh</span> <span class="at">-T</span> git@gitlab.tudelft.nl</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>The authenticity of host 'gitlab.tudelft.nl (192.30.255.112)' can't be established.
+RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
+This key is not known by any other names
+Are you sure you want to continue connecting (yes/no/[fingerprint])? y
+Please type 'yes', 'no' or the fingerprint: yes
+Warning: Permanently added 'gitlab.tudelft.nl' (RSA) to the list of known hosts.
+git@gitlab.tudelft.nl: Permission denied (publickey).</code></pre>
+</div>
+<p>Right, we forgot that we need to give GitLab our public key!</p>
+<p>First, we need to copy the public key. Be sure to include the
+<code>.pub</code> at the end, otherwise you’re looking at the private
+key.</p>
+<div class="codewrapper sourceCode" id="cb15">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="fu">cat</span> ~/.ssh/id_ed25519.pub</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDmRA3d51X0uu9wXek559gfn6UFNF69yZjChyBIU2qKI a.linguini@ratatouille.fr</code></pre>
+</div>
+<p>Now, going to the GitLab page in your browser, click on your profile
+icon in the top right corner of the left panel, then click on the
+<code>SSH Keys</code> link under <code>User Settings</code> in the same
+panel:</p>
+<figure><img src="fig/gitlab_ssh_keys.jpg" alt="The SSH Keys page in GitLab" class="figure mx-auto d-block"></figure><p>Click on the <code>Add new key</code> button, which will take you to
+a page like this:</p>
+<figure><img src="fig/gitlab_add_new_key.jpg" alt="Adding a new key in GitLab" class="figure mx-auto d-block"></figure><p>Here, you can paste your public key in the <code>Key</code> box, add
+a title, and set an expiration date. Once everything is filled in, you
+can click the <code>Add key</code> button.</p>
+<p>Now that we’ve set that up, let’s check our authentication again from
+the command line.</p>
+<div class="codewrapper sourceCode" id="cb17">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="ex">$</span> ssh <span class="at">-T</span> git@gitlab.tudelft.nl</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Welcome to GitLab, @alflin!</code></pre>
+</div>
+<p>Good! This output confirms that the SSH key works as intended. We are
+now ready to push our work to the remote repository.</p>
+</div>
+</div>
+<div class="section level3">
+<h3 id="push-local-changes-to-a-remote">Push local changes to a remote<a class="anchor" aria-label="anchor" href="#push-local-changes-to-a-remote"></a>
+</h3>
+<p>Now that authentication is setup, we can return to the remote. This
+command will push the changes from our local repository to the
+repository on GitHub:</p>
+<div class="codewrapper sourceCode" id="cb19">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="ex">$</span> git push origin main</span></code></pre>
+</div>
+<p>Since Alfredo set up a passphrase, it will prompt him for it. If you
+completed advanced settings for your authentication, it will not prompt
+for a passphrase.</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Enumerating objects: 16, done.
+Counting objects: 100% (16/16), done.
+Delta compression using up to 8 threads.
+Compressing objects: 100% (11/11), done.
+Writing objects: 100% (16/16), 1.45 KiB | 372.00 KiB/s, done.
+Total 16 (delta 2), reused 0 (delta 0)
+remote: Resolving deltas: 100% (2/2), done.
+To https://gitlab.tudelft.nl/alflin/recipes.git
+ * [new branch]      main -&gt; main</code></pre>
+</div>
+<div id="password-managers" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="password-managers" class="callout-inner">
+<h3 class="callout-title">Password Managers</h3>
+<div class="callout-content">
+<p>If your operating system has a password manager configured,
+<code>git push</code> will try to use it when it needs your username and
+password. For example, this is the default behavior for Git Bash on
+Windows. If you want to type your username and password at the terminal
+instead of using a password manager, type:</p>
+<div class="codewrapper sourceCode" id="cb21">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="ex">$</span> unset SSH_ASKPASS</span></code></pre>
+</div>
+<p>in the terminal, before you run <code>git push</code>. Despite the
+name, <a href="https://git-scm.com/docs/gitcredentials#_requesting_credentials" class="external-link">Git
+uses <code>SSH_ASKPASS</code> for all credential entry</a>, so you may
+want to unset <code>SSH_ASKPASS</code> whether you are using Git via SSH
+or https.</p>
+<p>You may also want to add <code>unset SSH_ASKPASS</code> at the end of
+your <code>~/.bashrc</code> to make Git default to using the terminal
+for usernames and passwords.</p>
+</div>
+</div>
+</div>
+<p>Our local and remote repositories are now in this state:</p>
+<figure><img src="fig/github-repo-after-first-push.svg" alt="GitLab repo after first push" class="figure mx-auto d-block"></figure><p>We can pull changes from the remote repository to the local one as
+well:</p>
+<div class="codewrapper sourceCode" id="cb22">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="ex">$</span> git pull origin main</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>From https://gitlab.tudelft.nl/alflin/recipes
+ * branch            main     -&gt; FETCH_HEAD
+Already up-to-date.</code></pre>
+</div>
+<p>Pulling has no effect in this case because the two repositories are
+already synchronized. If someone else had pushed some changes to the
+repository on GitHub, though, this command would download them to our
+local repository.</p>
+</div>
 </section><section><h2 class="section-heading" id="adding-project-members">Adding Project Members<a class="anchor" aria-label="anchor" href="#adding-project-members"></a>
 </h2>
 <hr class="half-width">
@@ -3929,7 +4268,7 @@ <h3 class="callout-title">Review Changes</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
 <div class="accordion-body">
 <p>On the command line, the Collaborator can use
 <code>git fetch origin main</code> to get the remote changes into the
@@ -4363,7 +4702,7 @@ <h3 class="callout-title">Conflicts on Non-textual files</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
 <div class="accordion-body">
 <p>Let’s try it. Suppose Alfredo takes a picture of its guacamole and
 calls it <code>guacamole.jpg</code>.</p>
@@ -4606,7 +4945,7 @@ <h3 class="callout-title">A Typical Work Session</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution3" aria-expanded="false" aria-controls="collapseSolution3">
   <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 </button>
-<div id="collapseSolution3" class="accordion-collapse collapse" aria-labelledby="headingSolution3" data-bs-parent="#accordionSolution3">
+<div id="collapseSolution3" class="accordion-collapse collapse" data-bs-parent="#accordionSolution3" aria-labelledby="headingSolution3">
 <div class="accordion-body">
 <table class="table">
 <colgroup>
@@ -5399,7 +5738,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-clean-code"><p>Content from <a href="clean-code.html">Clean Code</a></p>
 <hr>
-<p>Last updated on 2024-12-17 |
+<p>Last updated on 2024-12-19 |
 
         <a href="https://github.com/QuTech-Delft/prosoftdev-research/edit/main/episodes/clean-code.Rmd" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <div class="text-end">
@@ -6339,7 +6678,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
 <div class="accordion-body">
 <p>The above test breaks many of the “clean” tests and “clean” code
 principles:</p>
@@ -6416,12 +6755,12 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 </h3>
 <pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a><span class="ex">pip</span> install pylint</span></code></pre>
 </div>
-<div id="running-pyling-on-a-sample-program" class="callout">
+<div id="running-pylint-on-a-sample-program" class="callout">
 <div class="callout-square">
 <i class="callout-icon" data-feather="bell"></i>
 </div>
-<div id="running-pyling-on-a-sample-program" class="callout-inner">
-<h3 class="callout-title">Running Pyling on a sample program</h3>
+<div id="running-pylint-on-a-sample-program" class="callout-inner">
+<h3 class="callout-title">Running Pylint on a sample program</h3>
 <div class="callout-content">
 <div class="codewrapper sourceCode" id="cb24">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -6493,7 +6832,7 @@ <h3 class="callout-title">Challenge</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
 <div class="accordion-body">
 <div class="codewrapper sourceCode" id="cb26">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -6551,14 +6890,26 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <div class="section level3">
 <h3 id="pycharm-and-clean-code">PyCharm and Clean Code<a class="anchor" aria-label="anchor" href="#pycharm-and-clean-code"></a>
 </h3>
-<ul>
-<li>Introduce PyCharm, show how to setup a Python interpreter for a
-project</li>
-<li>Show how PyCharm is highlighting parts of the code that do not
-follow coding conventions</li>
-<li>Show how PyCharm can help with re-factoring - e.g. changing a
-variable/function name</li>
-</ul>
+<p>Using a modern development environment, such as PyCharm, can greatly
+facilitate writing clean code. In this section we will go over a few
+ways this can be accomplished.</p>
+<div id="configuring-a-python-interpreter-for-a-pycharm-project" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="configuring-a-python-interpreter-for-a-pycharm-project" class="callout-inner">
+<h3 class="callout-title">Configuring a Python interpreter for a PyCharm project</h3>
+<div class="callout-content">
+<p>For a given PyCharm project it is possible to setup a python
+interpreter, as shown below:</p>
+<figure><img src="fig/pycharm_python_interpreter.jpg" alt="Running Pytest from PyCharm" class="figure mx-auto d-block"></figure><p>The selected interpreter can be the system-wide one, or one selected
+from a virtual environment. Once a Python interpreter has been
+configured, PyCharm will use it to run code (e.g. <code>.py</code> files
+part of that project), or analyze the code and provide useful hints to
+the developer.</p>
+</div>
+</div>
+</div>
 </div>
 <div class="section level3">
 <h3 id="unit-tests-and-test-coverage">Unit Tests and Test Coverage<a class="anchor" aria-label="anchor" href="#unit-tests-and-test-coverage"></a>
@@ -6721,9 +7072,9 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/aio.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/aio.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/basic-git-commands.html b/basic-git-commands.html
index 19c3f97..343ef71 100644
--- a/basic-git-commands.html
+++ b/basic-git-commands.html
@@ -2228,9 +2228,9 @@ <h3 class="callout-title">Key Points</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/basic-git-commands.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/basic-git-commands.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-12-03",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/clean-code.html b/clean-code.html
index a3e5276..b45cf86 100644
--- a/clean-code.html
+++ b/clean-code.html
@@ -347,7 +347,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Clean Code</h1>
-        <p>Last updated on 2024-12-17 |
+        <p>Last updated on 2024-12-19 |
 
         <a href="https://github.com/QuTech-Delft/prosoftdev-research/edit/main/episodes/clean-code.Rmd" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -1258,7 +1258,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
 <div class="accordion-body">
 <p>The above test breaks many of the “clean” tests and “clean” code
 principles:</p>
@@ -1325,12 +1325,12 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 </h3>
 <pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a><span class="ex">pip</span> install pylint</span></code></pre>
 </div>
-<div id="running-pyling-on-a-sample-program" class="callout">
+<div id="running-pylint-on-a-sample-program" class="callout">
 <div class="callout-square">
 <i class="callout-icon" data-feather="bell"></i>
 </div>
-<div id="running-pyling-on-a-sample-program" class="callout-inner">
-<h3 class="callout-title">Running Pyling on a sample program</h3>
+<div id="running-pylint-on-a-sample-program" class="callout-inner">
+<h3 class="callout-title">Running Pylint on a sample program</h3>
 <div class="callout-content">
 <div class="codewrapper sourceCode" id="cb24">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -1402,7 +1402,7 @@ <h3 class="callout-title">Challenge</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
 <div class="accordion-body">
 <div class="codewrapper sourceCode" id="cb26">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -1459,13 +1459,27 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 <div class="section level3">
 <h3 id="pycharm-and-clean-code">PyCharm and Clean Code<a class="anchor" aria-label="anchor" href="#pycharm-and-clean-code"></a></h3>
-<ul><li>Introduce PyCharm, show how to setup a Python interpreter for a
-project</li>
-<li>Show how PyCharm is highlighting parts of the code that do not
-follow coding conventions</li>
-<li>Show how PyCharm can help with re-factoring - e.g. changing a
-variable/function name</li>
-</ul></div>
+<p>Using a modern development environment, such as PyCharm, can greatly
+facilitate writing clean code. In this section we will go over a few
+ways this can be accomplished.</p>
+<div id="configuring-a-python-interpreter-for-a-pycharm-project" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="configuring-a-python-interpreter-for-a-pycharm-project" class="callout-inner">
+<h3 class="callout-title">Configuring a Python interpreter for a PyCharm project</h3>
+<div class="callout-content">
+<p>For a given PyCharm project it is possible to setup a python
+interpreter, as shown below:</p>
+<figure><img src="fig/pycharm_python_interpreter.jpg" alt="Running Pytest from PyCharm" class="figure mx-auto d-block"></figure><p>The selected interpreter can be the system-wide one, or one selected
+from a virtual environment. Once a Python interpreter has been
+configured, PyCharm will use it to run code (e.g. <code>.py</code> files
+part of that project), or analyze the code and provide useful hints to
+the developer.</p>
+</div>
+</div>
+</div>
+</div>
 <div class="section level3">
 <h3 id="unit-tests-and-test-coverage">Unit Tests and Test Coverage<a class="anchor" aria-label="anchor" href="#unit-tests-and-test-coverage"></a></h3>
 <p><code>Pytest</code> is a simple yet powerful tool for testing Python
@@ -1605,9 +1619,9 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/clean-code.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/clean-code.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/credits.html b/credits.html
index f2a3a07..bdf4942 100644
--- a/credits.html
+++ b/credits.html
@@ -429,9 +429,9 @@ <h1>Credits</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/credits.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/credits.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-12-04",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/fig/git-freshly-made-gitlab-repo.svg b/fig/git-freshly-made-gitlab-repo.svg
new file mode 100644
index 0000000..4087fae
--- /dev/null
+++ b/fig/git-freshly-made-gitlab-repo.svg
@@ -0,0 +1,315 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Generator: Adobe Illustrator 15.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+
+<svg
+   xmlns:dc="http://purl.org/dc/elements/1.1/"
+   xmlns:cc="http://creativecommons.org/ns#"
+   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+   xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+   version="1.1"
+   x="0px"
+   y="0px"
+   width="610"
+   height="500"
+   viewBox="0 0 610 500"
+   enable-background="new 0 0 622 452"
+   xml:space="preserve"
+   id="svg2"
+   inkscape:version="0.91 r13725"
+   sodipodi:docname="git-freshly-made-github-repo.svg"><metadata
+     id="metadata134"><rdf:RDF><cc:Work
+         rdf:about=""><dc:format>image/svg+xml</dc:format><dc:type
+           rdf:resource="http://purl.org/dc/dcmitype/StillImage" /><dc:title></dc:title></cc:Work></rdf:RDF></metadata><defs
+     id="defs132" /><sodipodi:namedview
+     pagecolor="#ffffff"
+     bordercolor="#666666"
+     borderopacity="1"
+     objecttolerance="10"
+     gridtolerance="10"
+     guidetolerance="10"
+     inkscape:pageopacity="0"
+     inkscape:pageshadow="2"
+     inkscape:window-width="1362"
+     inkscape:window-height="729"
+     id="namedview130"
+     showgrid="false"
+     fit-margin-top="0"
+     fit-margin-left="0"
+     fit-margin-right="0"
+     fit-margin-bottom="0"
+     inkscape:zoom="0.6957385"
+     inkscape:cx="318.0608"
+     inkscape:cy="263.49478"
+     inkscape:window-x="0"
+     inkscape:window-y="18"
+     inkscape:window-maximized="0"
+     inkscape:current-layer="svg2" /><g
+     id="g3573"
+     transform="translate(-4.1425018,-9)"><g
+       id="g3564"><g
+         id="g3490"
+         transform="translate(0,250)"><rect
+           id="rect3492"
+           height="244"
+           width="603.78497"
+           stroke-miterlimit="10"
+           y="12"
+           x="7"
+           style="fill:#ffffff;stroke:#000000;stroke-miterlimit:10" /></g><g
+         id="g3494"
+         transform="translate(0,250)"><path
+           stroke-miterlimit="10"
+           d="m 598,63 c 0,-8.284 -6.716,-15 -15,-15 l -385,0 c -8.284,0 -15,6.716 -15,15 l 0,167 c 0,8.284 6.716,15 15,15 l 385,0 c 8.284,0 15,-6.716 15,-15 l 0,-167 z"
+           id="path3496"
+           inkscape:connector-curvature="0"
+           style="fill:#b5b5b5;stroke:#ffffff;stroke-miterlimit:10" /><rect
+           x="197"
+           y="59"
+           width="70"
+           height="28"
+           id="rect3498"
+           style="fill:none" /><text
+           transform="translate(197,71.4199)"
+           font-size="18"
+           id="text3500"
+           style="font-size:18px;font-family:Consolas">.git</text>
+</g><text
+         y="278.707"
+         x="16"
+         font-size="13.5"
+         id="text3502"
+         style="font-size:13.5px;font-family:Helvetica">https://gitlab.tudelft.nl/alflin/recipes.git</text>
+</g><g
+       id="g3504"><g
+         id="Layer_6"><rect
+           x="7"
+           y="12"
+           stroke-miterlimit="10"
+           width="603.78497"
+           height="244"
+           id="rect5"
+           style="fill:#ffffff;stroke:#000000;stroke-miterlimit:10" /></g><g
+         id="g8"><path
+           style="fill:#b5b5b5;stroke:#ffffff;stroke-miterlimit:10"
+           inkscape:connector-curvature="0"
+           id="path10"
+           d="m 598,63 c 0,-8.284 -6.716,-15 -15,-15 l -385,0 c -8.284,0 -15,6.716 -15,15 l 0,167 c 0,8.284 6.716,15 15,15 l 385,0 c 8.284,0 15,-6.716 15,-15 l 0,-167 z"
+           stroke-miterlimit="10" /><rect
+           style="fill:none"
+           id="rect12"
+           height="28"
+           width="70"
+           y="59"
+           x="197" /><text
+           style="font-size:18px;font-family:Consolas"
+           id="text14"
+           font-size="18"
+           transform="translate(197,71.4199)">.git</text>
+</g><rect
+         style="fill:none"
+         id="rect16"
+         height="24.448999"
+         width="195.58501"
+         y="19"
+         x="16" /><text
+         style="font-size:13.5px;font-family:Helvetica"
+         id="text18"
+         font-size="13.5"
+         x="16"
+         y="28.707001">~/alflin/recipes</text>
+<g
+         id="Layer_3"><g
+           id="g37"><linearGradient
+             id="SVGID_1_"
+             gradientUnits="userSpaceOnUse"
+             x1="303.49899"
+             y1="123.9863"
+             x2="303.49899"
+             y2="179.23489"><stop
+               offset="0.0982"
+               style="stop-color:#C4C4C4"
+               id="stop40" /><stop
+               offset="0.5326"
+               style="stop-color:#686868"
+               id="stop42" /><stop
+               offset="1"
+               style="stop-color:#000000"
+               id="stop44" /></linearGradient><path
+             stroke-miterlimit="10"
+             d="m 253.453,178.205 c 0,-9.264 22.404,-16.777 50.047,-16.777 27.643,0 50.045,7.514 50.045,16.777 l 0,1.029 c 0,0 0,-2.115 0,-3.117 0,-1.007 0,-35.745 0,-35.745 l 0,0.394 c 0,-9.27 -22.402,-16.78 -50.045,-16.78 -27.643,0 -50.047,7.51 -50.047,16.78 l 0,-0.394 c 0,0 0,34.519 0,35.733 0,1.205 0,3.129 0,3.129 l 0,-1.029 z"
+             id="path46"
+             inkscape:connector-curvature="0"
+             style="fill:url(#SVGID_1_);stroke:#231f20;stroke-miterlimit:10" /><g
+             id="g48"><path
+               stroke-miterlimit="10"
+               d="m 353.545,140.373 c 0,0 0,34.738 0,35.745 0,1.002 0.355,3.117 0.355,3.117 0,9.27 -22.758,16.779 -50.4,16.779 -27.642,0 -50.4,-7.51 -50.4,-16.779 0,0 0.354,-1.924 0.354,-3.129 0,-1.214 0,-35.733 0,-35.733 0,9.274 22.404,16.785 50.047,16.785 27.643,0 50.044,-7.511 50.044,-16.785 z"
+               id="path50"
+               inkscape:connector-curvature="0"
+               style="fill:#ffffff;stroke:#231f20;stroke-miterlimit:10" /></g></g><g
+           id="g52"><polygon
+             stroke-miterlimit="10"
+             points="328.542,149.459 341.719,134.965 282.411,134.965 269.235,149.459 "
+             id="polygon54"
+             style="fill:#ffffff;stroke:#000000;stroke-miterlimit:10" /><line
+             x1="282.41101"
+             y1="140.894"
+             x2="331.16501"
+             y2="140.894"
+             id="line56"
+             style="fill:none;stroke:#70bf41;stroke-width:2" /></g></g><g
+         id="Layer_4"><linearGradient
+           id="SVGID_2_"
+           gradientUnits="userSpaceOnUse"
+           x1="537.17682"
+           y1="57.660198"
+           x2="537.17682"
+           y2="112.9126"><stop
+             offset="0.0982"
+             style="stop-color:#C4C4C4"
+             id="stop60" /><stop
+             offset="0.5326"
+             style="stop-color:#686868"
+             id="stop62" /><stop
+             offset="1"
+             style="stop-color:#000000"
+             id="stop64" /></linearGradient><path
+           stroke-miterlimit="10"
+           d="m 487.13,111.882 c 0,-9.268 22.407,-16.781 50.047,-16.781 27.641,0 50.047,7.513 50.047,16.781 l 0,1.03 c 0,0 0,-2.118 0,-3.121 0,-1.003 0,-35.739 0,-35.739 l 0,0.388 c 0,-9.268 -22.406,-16.781 -50.047,-16.781 -27.64,0 -50.047,7.513 -50.047,16.781 l 0,-0.388 c 0,0 0,34.519 0,35.728 0,1.209 0,3.132 0,3.132 l 0,-1.03 z"
+           id="path66"
+           inkscape:connector-curvature="0"
+           style="fill:url(#SVGID_2_);stroke:#231f20;stroke-miterlimit:10" /><g
+           id="g68"><path
+             stroke-miterlimit="10"
+             d="m 587.021,151.283 c 0,0 0,34.738 0,35.74 0,1.002 0.354,3.121 0.354,3.121 0,9.268 -22.76,16.779 -50.4,16.779 -27.64,0 -50.399,-7.512 -50.399,-16.779 0,0 0.353,-1.924 0.353,-3.133 0,-1.209 0,-35.729 0,-35.729 0,9.268 22.407,16.781 50.047,16.781 27.638,0.001 50.045,-7.512 50.045,-16.78 z"
+             id="path70"
+             inkscape:connector-curvature="0"
+             style="fill:#ffffff;stroke:#231f20;stroke-miterlimit:10" /></g><g
+           id="g72"><path
+             stroke-miterlimit="10"
+             d="m 587.021,112.601 c 0,0 0,34.736 0,35.739 0,1.002 0.354,3.121 0.354,3.121 0,9.268 -22.76,16.779 -50.4,16.779 -27.64,0 -50.399,-7.512 -50.399,-16.779 0,0 0.353,-1.923 0.353,-3.132 0,-1.209 0,-35.728 0,-35.728 0,9.268 22.407,16.78 50.047,16.78 27.638,0 50.045,-7.512 50.045,-16.78 z"
+             id="path74"
+             inkscape:connector-curvature="0"
+             style="fill:#ffffff;stroke:#231f20;stroke-miterlimit:10" /></g><g
+           id="g76"><path
+             stroke-miterlimit="10"
+             d="m 587.021,73.628 c 0,0 0,34.737 0,35.739 0,1.002 0.354,3.12 0.354,3.12 0,9.269 -22.76,16.781 -50.4,16.781 -27.64,0 -50.399,-7.513 -50.399,-16.781 0,0 0.353,-1.922 0.353,-3.131 0,-1.209 0,-35.728 0,-35.728 0,9.268 22.407,16.78 50.047,16.78 27.638,0.001 50.045,-7.512 50.045,-16.78 z"
+             id="path78"
+             inkscape:connector-curvature="0"
+             style="fill:#ffffff;stroke:#231f20;stroke-miterlimit:10" /></g><g
+           id="g80"><polygon
+             stroke-miterlimit="10"
+             points="560.039,80.875 573.216,66.381 513.908,66.381 500.732,80.875 "
+             id="polygon82"
+             style="fill:#ffffff;stroke:#000000;stroke-miterlimit:10" /><line
+             x1="513.90802"
+             y1="72.310997"
+             x2="562.66199"
+             y2="72.310997"
+             id="line84"
+             style="fill:none;stroke:#70bf41;stroke-width:2" /></g></g><g
+         id="Layer_1"><g
+           id="g87"><rect
+             x="24"
+             y="85"
+             width="100"
+             height="128"
+             id="rect89"
+             style="fill:#dcdee0" /><rect
+             x="24"
+             y="85"
+             width="100"
+             height="128"
+             id="rect91"
+             style="fill:none;stroke:#85888d;stroke-width:2" /><line
+             x1="37"
+             y1="105"
+             x2="111"
+             y2="105"
+             id="line93"
+             style="fill:none;stroke:#000000;stroke-width:2" /><line
+             x1="37"
+             y1="111"
+             x2="111"
+             y2="111"
+             id="line95"
+             style="fill:none;stroke:#000000;stroke-width:2" /><line
+             x1="37"
+             y1="117"
+             x2="111"
+             y2="117"
+             id="line97"
+             style="fill:none;stroke:#000000;stroke-width:2" /><line
+             x1="37"
+             y1="129"
+             x2="111"
+             y2="129"
+             id="line99"
+             style="fill:none;stroke:#70bf41;stroke-width:2" /></g></g><g
+         id="Layer_2"><g
+           id="g102"><rect
+             x="150.871"
+             y="136.76801"
+             width="45.956001"
+             height="30.604"
+             id="rect104"
+             style="fill:#45beee" /><polygon
+             points="234.02,151.163 193.467,121.571 193.467,181.695 "
+             id="polygon106"
+             style="fill:#45beee" /></g><rect
+           x="164"
+           y="146.069"
+           width="52.743"
+           height="14"
+           id="rect108"
+           style="fill:none" /><text
+           transform="translate(164,154.3496)"
+           font-size="12"
+           id="text110"
+           style="font-size:12px;font-family:Consolas">git add</text>
+<g
+           id="g112"><rect
+             x="381.25101"
+             y="136.76801"
+             width="45.956001"
+             height="30.604"
+             id="rect114"
+             style="fill:#45beee" /><polygon
+             points="464.399,151.163 423.847,121.571 423.847,181.695 "
+             id="polygon116"
+             style="fill:#45beee" /></g><rect
+           x="376.98001"
+           y="146.069"
+           width="85.542"
+           height="14"
+           id="rect118"
+           style="fill:none" /><text
+           transform="translate(386.7637,154.3496)"
+           font-size="12"
+           id="text120"
+           style="font-size:12px;font-family:Consolas">git commit</text>
+<rect
+           x="229"
+           y="206"
+           width="147"
+           height="17"
+           id="rect122"
+           style="fill:none" /><text
+           transform="translate(269.4766,214.6279)"
+           font-size="12"
+           id="text124"
+           style="font-size:12px;font-family:Helvetica">staging area</text>
+<rect
+           x="464.785"
+           y="219"
+           width="147"
+           height="17"
+           id="rect126"
+           style="fill:none" /><text
+           transform="translate(511.9414,227.6279)"
+           font-size="12"
+           id="text128"
+           style="font-size:12px;font-family:Helvetica">repository</text>
+</g></g></g></svg>
\ No newline at end of file
diff --git a/fig/github-repo-after-first-push.svg b/fig/github-repo-after-first-push.svg
index e829035..9912054 100644
--- a/fig/github-repo-after-first-push.svg
+++ b/fig/github-repo-after-first-push.svg
@@ -20,7 +20,7 @@
    xml:space="preserve"
    id="svg4593"
    inkscape:version="0.91 r13725"
-   sodipodi:docname="github-repo-after-first-push.svg"><metadata
+   sodipodi:docname="gitlab-repo-after-first-push.svg"><metadata
      id="metadata4778"><rdf:RDF><cc:Work
          rdf:about=""><dc:format>image/svg+xml</dc:format><dc:type
            rdf:resource="http://purl.org/dc/dcmitype/StillImage" /><dc:title></dc:title></cc:Work></rdf:RDF></metadata><defs
@@ -126,7 +126,7 @@
                y="21.6"
                font-size="10.8"
                id="tspan4664"
-               style="font-size:10.80000019px;font-family:Consolas">origin https://github.com/alflin/recipes.git</tspan></text>
+               style="font-size:10.80000019px;font-family:Consolas">origin https://gitlab.tudelft.nl/alflin/recipes.git</tspan></text>
 </g><rect
            x="16"
            y="19"
@@ -390,7 +390,7 @@
            x="16"
            id="text4829"
            font-size="13.5"
-           style="font-size:13.5px;font-family:Helvetica">https://github.com/alflin/recipes.git</text>
+           style="font-size:13.5px;font-family:Helvetica">https://gitlab.tudelft.nl/alflin/recipes.git</text>
 <g
            transform="translate(0,250)"
            id="g5055"><g
diff --git a/fig/gitlab_add_new_key.jpg b/fig/gitlab_add_new_key.jpg
new file mode 100644
index 0000000..f631797
Binary files /dev/null and b/fig/gitlab_add_new_key.jpg differ
diff --git a/fig/gitlab_ssh_keys.jpg b/fig/gitlab_ssh_keys.jpg
new file mode 100644
index 0000000..119816b
Binary files /dev/null and b/fig/gitlab_ssh_keys.jpg differ
diff --git a/fig/gitlab_ssh_repo.jpg b/fig/gitlab_ssh_repo.jpg
new file mode 100644
index 0000000..ee949fe
Binary files /dev/null and b/fig/gitlab_ssh_repo.jpg differ
diff --git a/fig/pycharm_python_interpreter.jpg b/fig/pycharm_python_interpreter.jpg
new file mode 100644
index 0000000..2027582
Binary files /dev/null and b/fig/pycharm_python_interpreter.jpg differ
diff --git a/gitlab.html b/gitlab.html
index a408b0f..0e9eabf 100644
--- a/gitlab.html
+++ b/gitlab.html
@@ -246,6 +246,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
         <ul><li><a href="#introduction">Introduction</a></li>
 <li><a href="#navigation">Navigation</a></li>
 <li><a href="#gitlab-projects">GitLab Projects</a></li>
+<li><a href="#connecting-gitlab-projects-with-local-git-repositories">Connecting GitLab Projects with Local Git Repositories</a></li>
 <li><a href="#adding-project-members">Adding Project Members</a></li>
         </ul></div><!--/div.accordion-body-->
     </div><!--/div.accordion-collapse-->
@@ -347,7 +348,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>GitLab</h1>
-        <p>Last updated on 2024-12-17 |
+        <p>Last updated on 2024-12-19 |
 
         <a href="https://github.com/QuTech-Delft/prosoftdev-research/edit/main/episodes/gitlab.Rmd" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -602,6 +603,338 @@ <h3 id="archiving-a-project">Archiving a Project<a class="anchor" aria-label="an
 <p>At the bottom of the page is also a section for deleting a project,
 in case you ever think that is the right thing to do.</p>
 </div>
+</section><section><h2 class="section-heading" id="connecting-gitlab-projects-with-local-git-repositories">Connecting GitLab Projects with Local Git Repositories<a class="anchor" aria-label="anchor" href="#connecting-gitlab-projects-with-local-git-repositories"></a></h2>
+<hr class="half-width"><p>Remember from an earlier lesson that we have created a local Git
+repository that looked like this:</p>
+<figure><img src="fig/git-staging-area.svg" alt="Local repository with staging area" class="figure mx-auto d-block"></figure><p>Now we want to have a GitLab project that will be coupled with this
+local Git repo. The first step here is to follow the steps described in
+the previous section, and create a new GitLab project called ‘recipes’.
+Initially the Git repo for this GitLab project will be empty, as shown
+in the diagram below:</p>
+<figure><img src="fig/git-freshly-made-gitlab-repo.svg" alt="The local and remote Git repos" class="figure mx-auto d-block"></figure><div class="section level3">
+<h3 id="connecting-the-local-to-remote-repository">Connecting the local to remote repository<a class="anchor" aria-label="anchor" href="#connecting-the-local-to-remote-repository"></a></h3>
+<p>Now we connect the two repositories. We do this by making the GitHub
+repository a <a href="reference.html#remote">remote</a> for the local
+repository. Go to the home page of the repository on GitLab, click on
+the blue <code>Code</code> button, and copy the string below the
+<code>Clone with SSH</code></p>
+<figure><img src="fig/gitlab_ssh_repo.jpg" alt="Accessing a GitLab repo via SSH" class="figure mx-auto d-block"></figure><div id="https-vs.-ssh" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="https-vs.-ssh" class="callout-inner">
+<h3 class="callout-title">HTTPS vs. SSH</h3>
+<div class="callout-content">
+<p>We use SSH here because, while it requires some additional
+configuration, it is a security protocol widely used by many
+applications. The steps below describe SSH at a minimum level for
+GitLab.</p>
+</div>
+</div>
+</div>
+<p>With the <code>Clone with SSH</code> string you copied from the
+GitLab page, go into the local <code>recipes</code> repository, and run
+this command:</p>
+<div class="codewrapper sourceCode" id="cb1">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" tabindex="-1"></a><span class="ex">$</span> git remote add origin git@gitlab.tudelft.nl:alflin/recipes.git</span></code></pre>
+</div>
+<p>Make sure to use the URL for your repository rather than Alfredo’s:
+the only difference should be your username instead of
+<code>alflin</code>.</p>
+<p><code>origin</code> is a local name used to refer to the remote
+repository. It could be called anything, but <code>origin</code> is a
+convention that is often used by default in git and GitHub, so it’s
+helpful to stick with this unless there’s a reason not to.</p>
+<p>We can check that the command has worked by running
+<code>git remote -v</code>:</p>
+<div class="codewrapper sourceCode" id="cb2">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a><span class="ex">$</span> git remote <span class="at">-v</span></span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>origin   git@gitlab.tudelft.nl:alflin/recipes.git (fetch)
+origin   git@gitlab.tudelft.nl:alflin/recipes.git (push)</code></pre>
+</div>
+</div>
+<div class="section level3">
+<h3 id="ssh-background-and-setup">SSH Background and Setup<a class="anchor" aria-label="anchor" href="#ssh-background-and-setup"></a></h3>
+<p>Before Alfredo can connect to a remote repository, he needs to set up
+a way for his computer to authenticate with GitLab so it knows it’s him
+trying to connect to his remote repository.</p>
+<p>We are going to set up the method that is commonly used by many
+different services to authenticate access on the command line. This
+method is called Secure Shell Protocol (SSH). SSH is a cryptographic
+network protocol that allows secure communication between computers
+using an otherwise insecure network.</p>
+<p>SSH uses what is called a key pair. This is two keys that work
+together to validate access. One key is publicly known and called the
+public key, and the other key called the private key is kept private.
+Very descriptive names.</p>
+<p>You can think of the public key as a padlock, and only you have the
+key (the private key) to open it. You use the public key where you want
+a secure method of communication, such as your GitHub account. You give
+this padlock, or public key, to GitLab and say “lock the communications
+to my account with this so that only computers that have my private key
+can unlock communications and send git commands as my GitHub
+account.”</p>
+<p>What we will do now is the minimum required to set up the SSH keys
+and add the public key to a GitLab account.</p>
+<p>The first thing we are going to do is check if this has already been
+done on the computer you’re on. Because generally speaking, this setup
+only needs to happen once and then you can forget about it.</p>
+<div id="keeping-your-keys-secure" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="keeping-your-keys-secure" class="callout-inner">
+<h3 class="callout-title">Keeping your keys secure</h3>
+<div class="callout-content">
+<p>You shouldn’t really forget about your SSH keys, since they keep your
+account secure. It’s good practice to audit your secure shell keys every
+so often. Especially if you are using multiple computers to access your
+account.</p>
+</div>
+</div>
+</div>
+<p>We will run the list command to check what key pairs already exist on
+your computer.</p>
+<div class="codewrapper sourceCode" id="cb4">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" tabindex="-1"></a><span class="ex">$</span> ls <span class="at">-al</span> ~/.ssh</span></code></pre>
+</div>
+<p>Your output is going to look a little different depending on whether
+or not SSH has ever been set up on the computer you are using.</p>
+<p>Alfredo has not set up SSH on his computer, so his output is</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>ls: cannot access '/c/Users/Alfredo/.ssh': No such file or directory</code></pre>
+</div>
+<p>If SSH has been set up on the computer you’re using, the public and
+private key pairs will be listed. The file names are either
+<code>id_ed25519</code>/<code>id_ed25519.pub</code> or
+<code>id_rsa</code>/<code>id_rsa.pub</code> depending on how the key
+pairs were set up. Since they don’t exist on Alfredo’s computer, he uses
+this command to create them.</p>
+<div class="section level5">
+<h5 id="create-an-ssh-key-pair">Create an SSH key pair<a class="anchor" aria-label="anchor" href="#create-an-ssh-key-pair"></a></h5>
+<p>To create an SSH key pair Alfredo uses this command, where the
+<code>-t</code> option specifies which type of algorithm to use and
+<code>-C</code> attaches a comment to the key (here, Alfredo’s
+email):</p>
+<div class="codewrapper sourceCode" id="cb6">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" tabindex="-1"></a><span class="ex">$</span> ssh-keygen <span class="at">-t</span> ed25519 <span class="at">-C</span> <span class="st">"a.linguini@ratatouille.fr"</span></span></code></pre>
+</div>
+<p>If you are using a legacy system that doesn’t support the Ed25519
+algorithm, use:
+<code>$ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"</code></p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Generating public/private ed25519 key pair.
+Enter file in which to save the key (/c/Users/Alfredo/.ssh/id_ed25519):</code></pre>
+</div>
+<p>We want to use the default file, so just press <kbd>Enter</kbd>.</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Created directory '/c/Users/Alfredo/.ssh'.
+Enter passphrase (empty for no passphrase):</code></pre>
+</div>
+<p>Now, it is prompting Alfredo for a passphrase. Since he is using his
+kitchen’s laptop that other people sometimes have access to, he wants to
+create a passphrase. Be sure to use something memorable or save your
+passphrase somewhere, as there is no “reset my password” option. Note
+that, when typing a passphrase on a terminal, there won’t be any visual
+feedback of your typing. This is normal: your passphrase will be
+recorded even if you see nothing changing on your screen.</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Enter same passphrase again:</code></pre>
+</div>
+<p>After entering the same passphrase a second time, we receive the
+confirmation</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Your identification has been saved in /c/Users/Alfredo/.ssh/id_ed25519
+Your public key has been saved in /c/Users/Alfredo/.ssh/id_ed25519.pub
+The key fingerprint is:
+SHA256:SMSPIStNyA00KPxuYu94KpZgRAYjgt9g4BA4kFy3g1o a.linguini@ratatouille.fr
+The key's randomart image is:
++--[ED25519 256]--+
+|^B== o.          |
+|%*=.*.+          |
+|+=.E =.+         |
+| .=.+.o..        |
+|....  . S        |
+|.+ o             |
+|+ =              |
+|.o.o             |
+|oo+.             |
++----[SHA256]-----+</code></pre>
+</div>
+<p>The “identification” is actually the private key. You should never
+share it. The public key is appropriately named. The “key fingerprint”
+is a shorter version of a public key.</p>
+<p>Now that we have generated the SSH keys, we will find the SSH files
+when we check.</p>
+<div class="codewrapper sourceCode" id="cb11">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="fu">ls</span> <span class="at">-al</span> ~/.ssh</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>drwxr-xr-x 1 Alfredo   197121   0 Jul 16 14:48 ./
+drwxr-xr-x 1 Alfredo   197121   0 Jul 16 14:48 ../
+-rw-r--r-- 1 Alfredo   197121 419 Jul 16 14:48 id_ed25519
+-rw-r--r-- 1 Alfredo   197121 106 Jul 16 14:48 id_ed25519.pub</code></pre>
+</div>
+</div>
+<div class="section level5">
+<h5 id="copy-the-public-key-to-github">Copy the public key to GitHub<a class="anchor" aria-label="anchor" href="#copy-the-public-key-to-github"></a></h5>
+<p>Now we have a SSH key pair and we can run this command to check if
+GitHub can read our authentication.</p>
+<div class="codewrapper sourceCode" id="cb13">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="fu">ssh</span> <span class="at">-T</span> git@gitlab.tudelft.nl</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>The authenticity of host 'gitlab.tudelft.nl (192.30.255.112)' can't be established.
+RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
+This key is not known by any other names
+Are you sure you want to continue connecting (yes/no/[fingerprint])? y
+Please type 'yes', 'no' or the fingerprint: yes
+Warning: Permanently added 'gitlab.tudelft.nl' (RSA) to the list of known hosts.
+git@gitlab.tudelft.nl: Permission denied (publickey).</code></pre>
+</div>
+<p>Right, we forgot that we need to give GitLab our public key!</p>
+<p>First, we need to copy the public key. Be sure to include the
+<code>.pub</code> at the end, otherwise you’re looking at the private
+key.</p>
+<div class="codewrapper sourceCode" id="cb15">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="fu">cat</span> ~/.ssh/id_ed25519.pub</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDmRA3d51X0uu9wXek559gfn6UFNF69yZjChyBIU2qKI a.linguini@ratatouille.fr</code></pre>
+</div>
+<p>Now, going to the GitLab page in your browser, click on your profile
+icon in the top right corner of the left panel, then click on the
+<code>SSH Keys</code> link under <code>User Settings</code> in the same
+panel:</p>
+<figure><img src="fig/gitlab_ssh_keys.jpg" alt="The SSH Keys page in GitLab" class="figure mx-auto d-block"></figure><p>Click on the <code>Add new key</code> button, which will take you to
+a page like this:</p>
+<figure><img src="fig/gitlab_add_new_key.jpg" alt="Adding a new key in GitLab" class="figure mx-auto d-block"></figure><p>Here, you can paste your public key in the <code>Key</code> box, add
+a title, and set an expiration date. Once everything is filled in, you
+can click the <code>Add key</code> button.</p>
+<p>Now that we’ve set that up, let’s check our authentication again from
+the command line.</p>
+<div class="codewrapper sourceCode" id="cb17">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="ex">$</span> ssh <span class="at">-T</span> git@gitlab.tudelft.nl</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Welcome to GitLab, @alflin!</code></pre>
+</div>
+<p>Good! This output confirms that the SSH key works as intended. We are
+now ready to push our work to the remote repository.</p>
+</div>
+</div>
+<div class="section level3">
+<h3 id="push-local-changes-to-a-remote">Push local changes to a remote<a class="anchor" aria-label="anchor" href="#push-local-changes-to-a-remote"></a></h3>
+<p>Now that authentication is setup, we can return to the remote. This
+command will push the changes from our local repository to the
+repository on GitHub:</p>
+<div class="codewrapper sourceCode" id="cb19">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="ex">$</span> git push origin main</span></code></pre>
+</div>
+<p>Since Alfredo set up a passphrase, it will prompt him for it. If you
+completed advanced settings for your authentication, it will not prompt
+for a passphrase.</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Enumerating objects: 16, done.
+Counting objects: 100% (16/16), done.
+Delta compression using up to 8 threads.
+Compressing objects: 100% (11/11), done.
+Writing objects: 100% (16/16), 1.45 KiB | 372.00 KiB/s, done.
+Total 16 (delta 2), reused 0 (delta 0)
+remote: Resolving deltas: 100% (2/2), done.
+To https://gitlab.tudelft.nl/alflin/recipes.git
+ * [new branch]      main -&gt; main</code></pre>
+</div>
+<div id="password-managers" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="password-managers" class="callout-inner">
+<h3 class="callout-title">Password Managers</h3>
+<div class="callout-content">
+<p>If your operating system has a password manager configured,
+<code>git push</code> will try to use it when it needs your username and
+password. For example, this is the default behavior for Git Bash on
+Windows. If you want to type your username and password at the terminal
+instead of using a password manager, type:</p>
+<div class="codewrapper sourceCode" id="cb21">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="ex">$</span> unset SSH_ASKPASS</span></code></pre>
+</div>
+<p>in the terminal, before you run <code>git push</code>. Despite the
+name, <a href="https://git-scm.com/docs/gitcredentials#_requesting_credentials" class="external-link">Git
+uses <code>SSH_ASKPASS</code> for all credential entry</a>, so you may
+want to unset <code>SSH_ASKPASS</code> whether you are using Git via SSH
+or https.</p>
+<p>You may also want to add <code>unset SSH_ASKPASS</code> at the end of
+your <code>~/.bashrc</code> to make Git default to using the terminal
+for usernames and passwords.</p>
+</div>
+</div>
+</div>
+<p>Our local and remote repositories are now in this state:</p>
+<figure><img src="fig/github-repo-after-first-push.svg" alt="GitLab repo after first push" class="figure mx-auto d-block"></figure><p>We can pull changes from the remote repository to the local one as
+well:</p>
+<div class="codewrapper sourceCode" id="cb22">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="ex">$</span> git pull origin main</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>From https://gitlab.tudelft.nl/alflin/recipes
+ * branch            main     -&gt; FETCH_HEAD
+Already up-to-date.</code></pre>
+</div>
+<p>Pulling has no effect in this case because the two repositories are
+already synchronized. If someone else had pushed some changes to the
+repository on GitHub, though, this command would download them to our
+local repository.</p>
+</div>
 </section><section><h2 class="section-heading" id="adding-project-members">Adding Project Members<a class="anchor" aria-label="anchor" href="#adding-project-members"></a></h2>
 <hr class="half-width"><p>So far, each of you has created a GitLab project that no one but you
 can contribute to; depending on the visibility setting, no one but you
@@ -741,9 +1074,9 @@ <h3 class="callout-title">Key Points</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/gitlab.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/gitlab.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/images.html b/images.html
index 8fcabc3..d3df3c4 100644
--- a/images.html
+++ b/images.html
@@ -444,6 +444,24 @@ <h3 id="gitlab-figure-5">Figure 5</h3>
 <figure><img src="fig/new-project.png" alt="Project homepage for a new project" class="figure mx-auto d-block"><div class="figcaption">Fresh project homepage</div>
 </figure><hr>
 <h3 id="gitlab-figure-6">Figure 6</h3>
+<p aria-hidden="true">Image 1 of 1: ‘Local repository with staging area’</p>
+<figure><img src="fig/git-staging-area.svg" alt="Local repository with staging area" class="figure mx-auto d-block"></figure><hr>
+<h3 id="gitlab-figure-7">Figure 7</h3>
+<p aria-hidden="true">Image 1 of 1: ‘The local and remote Git repos’</p>
+<figure><img src="fig/git-freshly-made-gitlab-repo.svg" alt="The local and remote Git repos" class="figure mx-auto d-block"></figure><hr>
+<h3 id="gitlab-figure-8">Figure 8</h3>
+<p aria-hidden="true">Image 1 of 1: ‘Accessing a GitLab repo via SSH’</p>
+<figure><img src="fig/gitlab_ssh_repo.jpg" alt="Accessing a GitLab repo via SSH" class="figure mx-auto d-block"></figure><hr>
+<h3 id="gitlab-figure-9">Figure 9</h3>
+<p aria-hidden="true">Image 1 of 1: ‘The SSH Keys page in GitLab’</p>
+<figure><img src="fig/gitlab_ssh_keys.jpg" alt="The SSH Keys page in GitLab" class="figure mx-auto d-block"></figure><hr>
+<h3 id="gitlab-figure-10">Figure 10</h3>
+<p aria-hidden="true">Image 1 of 1: ‘Adding a new key in GitLab’</p>
+<figure><img src="fig/gitlab_add_new_key.jpg" alt="Adding a new key in GitLab" class="figure mx-auto d-block"></figure><hr>
+<h3 id="gitlab-figure-11">Figure 11</h3>
+<p aria-hidden="true">Image 1 of 1: ‘GitLab repo after first push’</p>
+<figure><img src="fig/github-repo-after-first-push.svg" alt="GitLab repo after first push" class="figure mx-auto d-block"></figure><hr>
+<h3 id="gitlab-figure-12">Figure 12</h3>
 <p aria-hidden="true">Image 1 of 1: ‘Project Members page’</p>
 <figure><img src="fig/initial-members.png" alt="Project Members page" class="figure mx-auto d-block"><div class="figcaption">Project members page</div>
 </figure><hr></section><section id="advanced-git-commands"><h2 class="section-heading"><a href="advanced-git-commands.html">Advanced Git Commands</a></h2>
@@ -530,6 +548,9 @@ <h3 id="clean-code-figure-2">Figure 2</h3>
 <figure><img src="fig/clean_code.png" alt="How to measure clean code?" class="figure mx-auto d-block"></figure><hr>
 <h3 id="clean-code-figure-3">Figure 3</h3>
 <p aria-hidden="true">Image 1 of 1: ‘Running Pytest from PyCharm’</p>
+<figure><img src="fig/pycharm_python_interpreter.jpg" alt="Running Pytest from PyCharm" class="figure mx-auto d-block"></figure><hr>
+<h3 id="clean-code-figure-4">Figure 4</h3>
+<p aria-hidden="true">Image 1 of 1: ‘Running Pytest from PyCharm’</p>
 <figure><img src="fig/pytest_pycharm.jpg" alt="Running Pytest from PyCharm" class="figure mx-auto d-block"></figure><hr></section><section id="credits"><h2 class="section-heading"><a href="credits.html">Credits</a></h2>
 <hr class="half-width"></section>
 </div>
@@ -578,9 +599,9 @@ <h3 id="clean-code-figure-3">Figure 3</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/images.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/images.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/index.html b/index.html
index 45c0c53..efd7c24 100644
--- a/index.html
+++ b/index.html
@@ -442,9 +442,9 @@ <h2 class="accordion-header" id="flush-headingTwelve">
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/index.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/index.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor-notes.html b/instructor-notes.html
index 6944726..248bf03 100644
--- a/instructor-notes.html
+++ b/instructor-notes.html
@@ -445,9 +445,9 @@ <h1>Instructor Notes</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor-notes.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor-notes.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/404.html b/instructor/404.html
index 9f9c934..3ccadf3 100644
--- a/instructor/404.html
+++ b/instructor/404.html
@@ -397,9 +397,9 @@ <h1>Page not found</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/404.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/404.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/CODE_OF_CONDUCT.html b/instructor/CODE_OF_CONDUCT.html
index bd815c5..702d873 100644
--- a/instructor/CODE_OF_CONDUCT.html
+++ b/instructor/CODE_OF_CONDUCT.html
@@ -417,9 +417,9 @@ <h1>Contributor Code of Conduct</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/CODE_OF_CONDUCT.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/CODE_OF_CONDUCT.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-11-18",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/LICENSE.html b/instructor/LICENSE.html
index 43f5bdf..f83b103 100644
--- a/instructor/LICENSE.html
+++ b/instructor/LICENSE.html
@@ -465,9 +465,9 @@ <h1>Licenses</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/LICENSE.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/LICENSE.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-11-18",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/advanced-git-commands.html b/instructor/advanced-git-commands.html
index d4698b7..878cae3 100644
--- a/instructor/advanced-git-commands.html
+++ b/instructor/advanced-git-commands.html
@@ -622,7 +622,7 @@ <h3 class="callout-title">Review Changes</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
 <div class="accordion-body">
 <p>On the command line, the Collaborator can use
 <code>git fetch origin main</code> to get the remote changes into the
@@ -1047,7 +1047,7 @@ <h3 class="callout-title">Conflicts on Non-textual files</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
 <div class="accordion-body">
 <p>Let’s try it. Suppose Alfredo takes a picture of its guacamole and
 calls it <code>guacamole.jpg</code>.</p>
@@ -1265,7 +1265,7 @@ <h3 class="callout-title">A Typical Work Session</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution3" aria-expanded="false" aria-controls="collapseSolution3">
   <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 </button>
-<div id="collapseSolution3" class="accordion-collapse collapse" aria-labelledby="headingSolution3" data-bs-parent="#accordionSolution3">
+<div id="collapseSolution3" class="accordion-collapse collapse" data-bs-parent="#accordionSolution3" aria-labelledby="headingSolution3">
 <div class="accordion-body">
 <table class="table"><colgroup><col width="6%"><col width="34%"><col width="59%"></colgroup><thead><tr class="header"><th>order</th>
 <th>action . . . . . .</th>
@@ -1386,9 +1386,9 @@ <h3 class="callout-title">Key Points</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/advanced-git-commands.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/advanced-git-commands.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-12-12",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/aio.html b/instructor/aio.html
index 420ebf9..e0f7f4b 100644
--- a/instructor/aio.html
+++ b/instructor/aio.html
@@ -3302,7 +3302,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-gitlab"><p>Content from <a href="gitlab.html">GitLab</a></p>
 <hr>
-<p>Last updated on 2024-12-17 |
+<p>Last updated on 2024-12-19 |
 
         <a href="https://github.com/QuTech-Delft/prosoftdev-research/edit/main/episodes/gitlab.Rmd" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <p>Estimated time: <i aria-hidden="true" data-feather="clock"></i> 40 minutes</p>
@@ -3564,6 +3564,345 @@ <h3 id="archiving-a-project">Archiving a Project<a class="anchor" aria-label="an
 <p>At the bottom of the page is also a section for deleting a project,
 in case you ever think that is the right thing to do.</p>
 </div>
+</section><section><h2 class="section-heading" id="connecting-gitlab-projects-with-local-git-repositories">Connecting GitLab Projects with Local Git Repositories<a class="anchor" aria-label="anchor" href="#connecting-gitlab-projects-with-local-git-repositories"></a>
+</h2>
+<hr class="half-width">
+<p>Remember from an earlier lesson that we have created a local Git
+repository that looked like this:</p>
+<figure><img src="../fig/git-staging-area.svg" alt="Local repository with staging area" class="figure mx-auto d-block"></figure><p>Now we want to have a GitLab project that will be coupled with this
+local Git repo. The first step here is to follow the steps described in
+the previous section, and create a new GitLab project called ‘recipes’.
+Initially the Git repo for this GitLab project will be empty, as shown
+in the diagram below:</p>
+<figure><img src="../fig/git-freshly-made-gitlab-repo.svg" alt="The local and remote Git repos" class="figure mx-auto d-block"></figure><div class="section level3">
+<h3 id="connecting-the-local-to-remote-repository">Connecting the local to remote repository<a class="anchor" aria-label="anchor" href="#connecting-the-local-to-remote-repository"></a>
+</h3>
+<p>Now we connect the two repositories. We do this by making the GitHub
+repository a <a href="reference.html#remote">remote</a> for the local
+repository. Go to the home page of the repository on GitLab, click on
+the blue <code>Code</code> button, and copy the string below the
+<code>Clone with SSH</code></p>
+<figure><img src="../fig/gitlab_ssh_repo.jpg" alt="Accessing a GitLab repo via SSH" class="figure mx-auto d-block"></figure><div id="https-vs.-ssh" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="https-vs.-ssh" class="callout-inner">
+<h3 class="callout-title">HTTPS vs. SSH</h3>
+<div class="callout-content">
+<p>We use SSH here because, while it requires some additional
+configuration, it is a security protocol widely used by many
+applications. The steps below describe SSH at a minimum level for
+GitLab.</p>
+</div>
+</div>
+</div>
+<p>With the <code>Clone with SSH</code> string you copied from the
+GitLab page, go into the local <code>recipes</code> repository, and run
+this command:</p>
+<div class="codewrapper sourceCode" id="cb1">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" tabindex="-1"></a><span class="ex">$</span> git remote add origin git@gitlab.tudelft.nl:alflin/recipes.git</span></code></pre>
+</div>
+<p>Make sure to use the URL for your repository rather than Alfredo’s:
+the only difference should be your username instead of
+<code>alflin</code>.</p>
+<p><code>origin</code> is a local name used to refer to the remote
+repository. It could be called anything, but <code>origin</code> is a
+convention that is often used by default in git and GitHub, so it’s
+helpful to stick with this unless there’s a reason not to.</p>
+<p>We can check that the command has worked by running
+<code>git remote -v</code>:</p>
+<div class="codewrapper sourceCode" id="cb2">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a><span class="ex">$</span> git remote <span class="at">-v</span></span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>origin   git@gitlab.tudelft.nl:alflin/recipes.git (fetch)
+origin   git@gitlab.tudelft.nl:alflin/recipes.git (push)</code></pre>
+</div>
+</div>
+<div class="section level3">
+<h3 id="ssh-background-and-setup">SSH Background and Setup<a class="anchor" aria-label="anchor" href="#ssh-background-and-setup"></a>
+</h3>
+<p>Before Alfredo can connect to a remote repository, he needs to set up
+a way for his computer to authenticate with GitLab so it knows it’s him
+trying to connect to his remote repository.</p>
+<p>We are going to set up the method that is commonly used by many
+different services to authenticate access on the command line. This
+method is called Secure Shell Protocol (SSH). SSH is a cryptographic
+network protocol that allows secure communication between computers
+using an otherwise insecure network.</p>
+<p>SSH uses what is called a key pair. This is two keys that work
+together to validate access. One key is publicly known and called the
+public key, and the other key called the private key is kept private.
+Very descriptive names.</p>
+<p>You can think of the public key as a padlock, and only you have the
+key (the private key) to open it. You use the public key where you want
+a secure method of communication, such as your GitHub account. You give
+this padlock, or public key, to GitLab and say “lock the communications
+to my account with this so that only computers that have my private key
+can unlock communications and send git commands as my GitHub
+account.”</p>
+<p>What we will do now is the minimum required to set up the SSH keys
+and add the public key to a GitLab account.</p>
+<p>The first thing we are going to do is check if this has already been
+done on the computer you’re on. Because generally speaking, this setup
+only needs to happen once and then you can forget about it.</p>
+<div id="keeping-your-keys-secure" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="keeping-your-keys-secure" class="callout-inner">
+<h3 class="callout-title">Keeping your keys secure</h3>
+<div class="callout-content">
+<p>You shouldn’t really forget about your SSH keys, since they keep your
+account secure. It’s good practice to audit your secure shell keys every
+so often. Especially if you are using multiple computers to access your
+account.</p>
+</div>
+</div>
+</div>
+<p>We will run the list command to check what key pairs already exist on
+your computer.</p>
+<div class="codewrapper sourceCode" id="cb4">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" tabindex="-1"></a><span class="ex">$</span> ls <span class="at">-al</span> ~/.ssh</span></code></pre>
+</div>
+<p>Your output is going to look a little different depending on whether
+or not SSH has ever been set up on the computer you are using.</p>
+<p>Alfredo has not set up SSH on his computer, so his output is</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>ls: cannot access '/c/Users/Alfredo/.ssh': No such file or directory</code></pre>
+</div>
+<p>If SSH has been set up on the computer you’re using, the public and
+private key pairs will be listed. The file names are either
+<code>id_ed25519</code>/<code>id_ed25519.pub</code> or
+<code>id_rsa</code>/<code>id_rsa.pub</code> depending on how the key
+pairs were set up. Since they don’t exist on Alfredo’s computer, he uses
+this command to create them.</p>
+<div class="section level5">
+<h5 id="create-an-ssh-key-pair">Create an SSH key pair<a class="anchor" aria-label="anchor" href="#create-an-ssh-key-pair"></a>
+</h5>
+<p>To create an SSH key pair Alfredo uses this command, where the
+<code>-t</code> option specifies which type of algorithm to use and
+<code>-C</code> attaches a comment to the key (here, Alfredo’s
+email):</p>
+<div class="codewrapper sourceCode" id="cb6">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" tabindex="-1"></a><span class="ex">$</span> ssh-keygen <span class="at">-t</span> ed25519 <span class="at">-C</span> <span class="st">"a.linguini@ratatouille.fr"</span></span></code></pre>
+</div>
+<p>If you are using a legacy system that doesn’t support the Ed25519
+algorithm, use:
+<code>$ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"</code></p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Generating public/private ed25519 key pair.
+Enter file in which to save the key (/c/Users/Alfredo/.ssh/id_ed25519):</code></pre>
+</div>
+<p>We want to use the default file, so just press <kbd>Enter</kbd>.</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Created directory '/c/Users/Alfredo/.ssh'.
+Enter passphrase (empty for no passphrase):</code></pre>
+</div>
+<p>Now, it is prompting Alfredo for a passphrase. Since he is using his
+kitchen’s laptop that other people sometimes have access to, he wants to
+create a passphrase. Be sure to use something memorable or save your
+passphrase somewhere, as there is no “reset my password” option. Note
+that, when typing a passphrase on a terminal, there won’t be any visual
+feedback of your typing. This is normal: your passphrase will be
+recorded even if you see nothing changing on your screen.</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Enter same passphrase again:</code></pre>
+</div>
+<p>After entering the same passphrase a second time, we receive the
+confirmation</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Your identification has been saved in /c/Users/Alfredo/.ssh/id_ed25519
+Your public key has been saved in /c/Users/Alfredo/.ssh/id_ed25519.pub
+The key fingerprint is:
+SHA256:SMSPIStNyA00KPxuYu94KpZgRAYjgt9g4BA4kFy3g1o a.linguini@ratatouille.fr
+The key's randomart image is:
++--[ED25519 256]--+
+|^B== o.          |
+|%*=.*.+          |
+|+=.E =.+         |
+| .=.+.o..        |
+|....  . S        |
+|.+ o             |
+|+ =              |
+|.o.o             |
+|oo+.             |
++----[SHA256]-----+</code></pre>
+</div>
+<p>The “identification” is actually the private key. You should never
+share it. The public key is appropriately named. The “key fingerprint”
+is a shorter version of a public key.</p>
+<p>Now that we have generated the SSH keys, we will find the SSH files
+when we check.</p>
+<div class="codewrapper sourceCode" id="cb11">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="fu">ls</span> <span class="at">-al</span> ~/.ssh</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>drwxr-xr-x 1 Alfredo   197121   0 Jul 16 14:48 ./
+drwxr-xr-x 1 Alfredo   197121   0 Jul 16 14:48 ../
+-rw-r--r-- 1 Alfredo   197121 419 Jul 16 14:48 id_ed25519
+-rw-r--r-- 1 Alfredo   197121 106 Jul 16 14:48 id_ed25519.pub</code></pre>
+</div>
+</div>
+<div class="section level5">
+<h5 id="copy-the-public-key-to-github">Copy the public key to GitHub<a class="anchor" aria-label="anchor" href="#copy-the-public-key-to-github"></a>
+</h5>
+<p>Now we have a SSH key pair and we can run this command to check if
+GitHub can read our authentication.</p>
+<div class="codewrapper sourceCode" id="cb13">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="fu">ssh</span> <span class="at">-T</span> git@gitlab.tudelft.nl</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>The authenticity of host 'gitlab.tudelft.nl (192.30.255.112)' can't be established.
+RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
+This key is not known by any other names
+Are you sure you want to continue connecting (yes/no/[fingerprint])? y
+Please type 'yes', 'no' or the fingerprint: yes
+Warning: Permanently added 'gitlab.tudelft.nl' (RSA) to the list of known hosts.
+git@gitlab.tudelft.nl: Permission denied (publickey).</code></pre>
+</div>
+<p>Right, we forgot that we need to give GitLab our public key!</p>
+<p>First, we need to copy the public key. Be sure to include the
+<code>.pub</code> at the end, otherwise you’re looking at the private
+key.</p>
+<div class="codewrapper sourceCode" id="cb15">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="fu">cat</span> ~/.ssh/id_ed25519.pub</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDmRA3d51X0uu9wXek559gfn6UFNF69yZjChyBIU2qKI a.linguini@ratatouille.fr</code></pre>
+</div>
+<p>Now, going to the GitLab page in your browser, click on your profile
+icon in the top right corner of the left panel, then click on the
+<code>SSH Keys</code> link under <code>User Settings</code> in the same
+panel:</p>
+<figure><img src="../fig/gitlab_ssh_keys.jpg" alt="The SSH Keys page in GitLab" class="figure mx-auto d-block"></figure><p>Click on the <code>Add new key</code> button, which will take you to
+a page like this:</p>
+<figure><img src="../fig/gitlab_add_new_key.jpg" alt="Adding a new key in GitLab" class="figure mx-auto d-block"></figure><p>Here, you can paste your public key in the <code>Key</code> box, add
+a title, and set an expiration date. Once everything is filled in, you
+can click the <code>Add key</code> button.</p>
+<p>Now that we’ve set that up, let’s check our authentication again from
+the command line.</p>
+<div class="codewrapper sourceCode" id="cb17">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="ex">$</span> ssh <span class="at">-T</span> git@gitlab.tudelft.nl</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Welcome to GitLab, @alflin!</code></pre>
+</div>
+<p>Good! This output confirms that the SSH key works as intended. We are
+now ready to push our work to the remote repository.</p>
+</div>
+</div>
+<div class="section level3">
+<h3 id="push-local-changes-to-a-remote">Push local changes to a remote<a class="anchor" aria-label="anchor" href="#push-local-changes-to-a-remote"></a>
+</h3>
+<p>Now that authentication is setup, we can return to the remote. This
+command will push the changes from our local repository to the
+repository on GitHub:</p>
+<div class="codewrapper sourceCode" id="cb19">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="ex">$</span> git push origin main</span></code></pre>
+</div>
+<p>Since Alfredo set up a passphrase, it will prompt him for it. If you
+completed advanced settings for your authentication, it will not prompt
+for a passphrase.</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Enumerating objects: 16, done.
+Counting objects: 100% (16/16), done.
+Delta compression using up to 8 threads.
+Compressing objects: 100% (11/11), done.
+Writing objects: 100% (16/16), 1.45 KiB | 372.00 KiB/s, done.
+Total 16 (delta 2), reused 0 (delta 0)
+remote: Resolving deltas: 100% (2/2), done.
+To https://gitlab.tudelft.nl/alflin/recipes.git
+ * [new branch]      main -&gt; main</code></pre>
+</div>
+<div id="password-managers" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="password-managers" class="callout-inner">
+<h3 class="callout-title">Password Managers</h3>
+<div class="callout-content">
+<p>If your operating system has a password manager configured,
+<code>git push</code> will try to use it when it needs your username and
+password. For example, this is the default behavior for Git Bash on
+Windows. If you want to type your username and password at the terminal
+instead of using a password manager, type:</p>
+<div class="codewrapper sourceCode" id="cb21">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="ex">$</span> unset SSH_ASKPASS</span></code></pre>
+</div>
+<p>in the terminal, before you run <code>git push</code>. Despite the
+name, <a href="https://git-scm.com/docs/gitcredentials#_requesting_credentials" class="external-link">Git
+uses <code>SSH_ASKPASS</code> for all credential entry</a>, so you may
+want to unset <code>SSH_ASKPASS</code> whether you are using Git via SSH
+or https.</p>
+<p>You may also want to add <code>unset SSH_ASKPASS</code> at the end of
+your <code>~/.bashrc</code> to make Git default to using the terminal
+for usernames and passwords.</p>
+</div>
+</div>
+</div>
+<p>Our local and remote repositories are now in this state:</p>
+<figure><img src="../fig/github-repo-after-first-push.svg" alt="GitLab repo after first push" class="figure mx-auto d-block"></figure><p>We can pull changes from the remote repository to the local one as
+well:</p>
+<div class="codewrapper sourceCode" id="cb22">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="ex">$</span> git pull origin main</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>From https://gitlab.tudelft.nl/alflin/recipes
+ * branch            main     -&gt; FETCH_HEAD
+Already up-to-date.</code></pre>
+</div>
+<p>Pulling has no effect in this case because the two repositories are
+already synchronized. If someone else had pushed some changes to the
+repository on GitHub, though, this command would download them to our
+local repository.</p>
+</div>
 </section><section><h2 class="section-heading" id="adding-project-members">Adding Project Members<a class="anchor" aria-label="anchor" href="#adding-project-members"></a>
 </h2>
 <hr class="half-width">
@@ -3936,7 +4275,7 @@ <h3 class="callout-title">Review Changes</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
 <div class="accordion-body">
 <p>On the command line, the Collaborator can use
 <code>git fetch origin main</code> to get the remote changes into the
@@ -4370,7 +4709,7 @@ <h3 class="callout-title">Conflicts on Non-textual files</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
 <div class="accordion-body">
 <p>Let’s try it. Suppose Alfredo takes a picture of its guacamole and
 calls it <code>guacamole.jpg</code>.</p>
@@ -4613,7 +4952,7 @@ <h3 class="callout-title">A Typical Work Session</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution3" aria-expanded="false" aria-controls="collapseSolution3">
   <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 </button>
-<div id="collapseSolution3" class="accordion-collapse collapse" aria-labelledby="headingSolution3" data-bs-parent="#accordionSolution3">
+<div id="collapseSolution3" class="accordion-collapse collapse" data-bs-parent="#accordionSolution3" aria-labelledby="headingSolution3">
 <div class="accordion-body">
 <table class="table">
 <colgroup>
@@ -5407,7 +5746,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-clean-code"><p>Content from <a href="clean-code.html">Clean Code</a></p>
 <hr>
-<p>Last updated on 2024-12-17 |
+<p>Last updated on 2024-12-19 |
 
         <a href="https://github.com/QuTech-Delft/prosoftdev-research/edit/main/episodes/clean-code.Rmd" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <p>Estimated time: <i aria-hidden="true" data-feather="clock"></i> 180 minutes</p>
@@ -6348,7 +6687,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
 <div class="accordion-body">
 <p>The above test breaks many of the “clean” tests and “clean” code
 principles:</p>
@@ -6425,12 +6764,12 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 </h3>
 <pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a><span class="ex">pip</span> install pylint</span></code></pre>
 </div>
-<div id="running-pyling-on-a-sample-program" class="callout">
+<div id="running-pylint-on-a-sample-program" class="callout">
 <div class="callout-square">
 <i class="callout-icon" data-feather="bell"></i>
 </div>
-<div id="running-pyling-on-a-sample-program" class="callout-inner">
-<h3 class="callout-title">Running Pyling on a sample program</h3>
+<div id="running-pylint-on-a-sample-program" class="callout-inner">
+<h3 class="callout-title">Running Pylint on a sample program</h3>
 <div class="callout-content">
 <div class="codewrapper sourceCode" id="cb24">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -6502,7 +6841,7 @@ <h3 class="callout-title">Challenge</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
 <div class="accordion-body">
 <div class="codewrapper sourceCode" id="cb26">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -6560,14 +6899,26 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <div class="section level3">
 <h3 id="pycharm-and-clean-code">PyCharm and Clean Code<a class="anchor" aria-label="anchor" href="#pycharm-and-clean-code"></a>
 </h3>
-<ul>
-<li>Introduce PyCharm, show how to setup a Python interpreter for a
-project</li>
-<li>Show how PyCharm is highlighting parts of the code that do not
-follow coding conventions</li>
-<li>Show how PyCharm can help with re-factoring - e.g. changing a
-variable/function name</li>
-</ul>
+<p>Using a modern development environment, such as PyCharm, can greatly
+facilitate writing clean code. In this section we will go over a few
+ways this can be accomplished.</p>
+<div id="configuring-a-python-interpreter-for-a-pycharm-project" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="configuring-a-python-interpreter-for-a-pycharm-project" class="callout-inner">
+<h3 class="callout-title">Configuring a Python interpreter for a PyCharm project</h3>
+<div class="callout-content">
+<p>For a given PyCharm project it is possible to setup a python
+interpreter, as shown below:</p>
+<figure><img src="../fig/pycharm_python_interpreter.jpg" alt="Running Pytest from PyCharm" class="figure mx-auto d-block"></figure><p>The selected interpreter can be the system-wide one, or one selected
+from a virtual environment. Once a Python interpreter has been
+configured, PyCharm will use it to run code (e.g. <code>.py</code> files
+part of that project), or analyze the code and provide useful hints to
+the developer.</p>
+</div>
+</div>
+</div>
 </div>
 <div class="section level3">
 <h3 id="unit-tests-and-test-coverage">Unit Tests and Test Coverage<a class="anchor" aria-label="anchor" href="#unit-tests-and-test-coverage"></a>
@@ -6730,9 +7081,9 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/aio.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/aio.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/basic-git-commands.html b/instructor/basic-git-commands.html
index 5137b6e..fb48b60 100644
--- a/instructor/basic-git-commands.html
+++ b/instructor/basic-git-commands.html
@@ -2230,9 +2230,9 @@ <h3 class="callout-title">Key Points</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/basic-git-commands.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/basic-git-commands.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-12-03",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/clean-code.html b/instructor/clean-code.html
index 470f43d..eb092e7 100644
--- a/instructor/clean-code.html
+++ b/instructor/clean-code.html
@@ -347,7 +347,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Clean Code</h1>
-        <p>Last updated on 2024-12-17 |
+        <p>Last updated on 2024-12-19 |
 
         <a href="https://github.com/QuTech-Delft/prosoftdev-research/edit/main/episodes/clean-code.Rmd" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -1260,7 +1260,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
 <div class="accordion-body">
 <p>The above test breaks many of the “clean” tests and “clean” code
 principles:</p>
@@ -1327,12 +1327,12 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 </h3>
 <pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a><span class="ex">pip</span> install pylint</span></code></pre>
 </div>
-<div id="running-pyling-on-a-sample-program" class="callout">
+<div id="running-pylint-on-a-sample-program" class="callout">
 <div class="callout-square">
 <i class="callout-icon" data-feather="bell"></i>
 </div>
-<div id="running-pyling-on-a-sample-program" class="callout-inner">
-<h3 class="callout-title">Running Pyling on a sample program</h3>
+<div id="running-pylint-on-a-sample-program" class="callout-inner">
+<h3 class="callout-title">Running Pylint on a sample program</h3>
 <div class="callout-content">
 <div class="codewrapper sourceCode" id="cb24">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -1404,7 +1404,7 @@ <h3 class="callout-title">Challenge</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
 <div class="accordion-body">
 <div class="codewrapper sourceCode" id="cb26">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -1461,13 +1461,27 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 <div class="section level3">
 <h3 id="pycharm-and-clean-code">PyCharm and Clean Code<a class="anchor" aria-label="anchor" href="#pycharm-and-clean-code"></a></h3>
-<ul><li>Introduce PyCharm, show how to setup a Python interpreter for a
-project</li>
-<li>Show how PyCharm is highlighting parts of the code that do not
-follow coding conventions</li>
-<li>Show how PyCharm can help with re-factoring - e.g. changing a
-variable/function name</li>
-</ul></div>
+<p>Using a modern development environment, such as PyCharm, can greatly
+facilitate writing clean code. In this section we will go over a few
+ways this can be accomplished.</p>
+<div id="configuring-a-python-interpreter-for-a-pycharm-project" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="configuring-a-python-interpreter-for-a-pycharm-project" class="callout-inner">
+<h3 class="callout-title">Configuring a Python interpreter for a PyCharm project</h3>
+<div class="callout-content">
+<p>For a given PyCharm project it is possible to setup a python
+interpreter, as shown below:</p>
+<figure><img src="../fig/pycharm_python_interpreter.jpg" alt="Running Pytest from PyCharm" class="figure mx-auto d-block"></figure><p>The selected interpreter can be the system-wide one, or one selected
+from a virtual environment. Once a Python interpreter has been
+configured, PyCharm will use it to run code (e.g. <code>.py</code> files
+part of that project), or analyze the code and provide useful hints to
+the developer.</p>
+</div>
+</div>
+</div>
+</div>
 <div class="section level3">
 <h3 id="unit-tests-and-test-coverage">Unit Tests and Test Coverage<a class="anchor" aria-label="anchor" href="#unit-tests-and-test-coverage"></a></h3>
 <p><code>Pytest</code> is a simple yet powerful tool for testing Python
@@ -1607,9 +1621,9 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/clean-code.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/clean-code.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/credits.html b/instructor/credits.html
index 20c80fe..c0775d7 100644
--- a/instructor/credits.html
+++ b/instructor/credits.html
@@ -431,9 +431,9 @@ <h1>Credits</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/credits.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/credits.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-12-04",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/gitlab.html b/instructor/gitlab.html
index 6d841af..5703f65 100644
--- a/instructor/gitlab.html
+++ b/instructor/gitlab.html
@@ -246,6 +246,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
         <ul><li><a href="#introduction">Introduction</a></li>
 <li><a href="#navigation">Navigation</a></li>
 <li><a href="#gitlab-projects">GitLab Projects</a></li>
+<li><a href="#connecting-gitlab-projects-with-local-git-repositories">Connecting GitLab Projects with Local Git Repositories</a></li>
 <li><a href="#adding-project-members">Adding Project Members</a></li>
         </ul></div><!--/div.accordion-body-->
     </div><!--/div.accordion-collapse-->
@@ -347,7 +348,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>GitLab</h1>
-        <p>Last updated on 2024-12-17 |
+        <p>Last updated on 2024-12-19 |
 
         <a href="https://github.com/QuTech-Delft/prosoftdev-research/edit/main/episodes/gitlab.Rmd" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -604,6 +605,338 @@ <h3 id="archiving-a-project">Archiving a Project<a class="anchor" aria-label="an
 <p>At the bottom of the page is also a section for deleting a project,
 in case you ever think that is the right thing to do.</p>
 </div>
+</section><section><h2 class="section-heading" id="connecting-gitlab-projects-with-local-git-repositories">Connecting GitLab Projects with Local Git Repositories<a class="anchor" aria-label="anchor" href="#connecting-gitlab-projects-with-local-git-repositories"></a></h2>
+<hr class="half-width"><p>Remember from an earlier lesson that we have created a local Git
+repository that looked like this:</p>
+<figure><img src="../fig/git-staging-area.svg" alt="Local repository with staging area" class="figure mx-auto d-block"></figure><p>Now we want to have a GitLab project that will be coupled with this
+local Git repo. The first step here is to follow the steps described in
+the previous section, and create a new GitLab project called ‘recipes’.
+Initially the Git repo for this GitLab project will be empty, as shown
+in the diagram below:</p>
+<figure><img src="../fig/git-freshly-made-gitlab-repo.svg" alt="The local and remote Git repos" class="figure mx-auto d-block"></figure><div class="section level3">
+<h3 id="connecting-the-local-to-remote-repository">Connecting the local to remote repository<a class="anchor" aria-label="anchor" href="#connecting-the-local-to-remote-repository"></a></h3>
+<p>Now we connect the two repositories. We do this by making the GitHub
+repository a <a href="reference.html#remote">remote</a> for the local
+repository. Go to the home page of the repository on GitLab, click on
+the blue <code>Code</code> button, and copy the string below the
+<code>Clone with SSH</code></p>
+<figure><img src="../fig/gitlab_ssh_repo.jpg" alt="Accessing a GitLab repo via SSH" class="figure mx-auto d-block"></figure><div id="https-vs.-ssh" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="https-vs.-ssh" class="callout-inner">
+<h3 class="callout-title">HTTPS vs. SSH</h3>
+<div class="callout-content">
+<p>We use SSH here because, while it requires some additional
+configuration, it is a security protocol widely used by many
+applications. The steps below describe SSH at a minimum level for
+GitLab.</p>
+</div>
+</div>
+</div>
+<p>With the <code>Clone with SSH</code> string you copied from the
+GitLab page, go into the local <code>recipes</code> repository, and run
+this command:</p>
+<div class="codewrapper sourceCode" id="cb1">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" tabindex="-1"></a><span class="ex">$</span> git remote add origin git@gitlab.tudelft.nl:alflin/recipes.git</span></code></pre>
+</div>
+<p>Make sure to use the URL for your repository rather than Alfredo’s:
+the only difference should be your username instead of
+<code>alflin</code>.</p>
+<p><code>origin</code> is a local name used to refer to the remote
+repository. It could be called anything, but <code>origin</code> is a
+convention that is often used by default in git and GitHub, so it’s
+helpful to stick with this unless there’s a reason not to.</p>
+<p>We can check that the command has worked by running
+<code>git remote -v</code>:</p>
+<div class="codewrapper sourceCode" id="cb2">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a><span class="ex">$</span> git remote <span class="at">-v</span></span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>origin   git@gitlab.tudelft.nl:alflin/recipes.git (fetch)
+origin   git@gitlab.tudelft.nl:alflin/recipes.git (push)</code></pre>
+</div>
+</div>
+<div class="section level3">
+<h3 id="ssh-background-and-setup">SSH Background and Setup<a class="anchor" aria-label="anchor" href="#ssh-background-and-setup"></a></h3>
+<p>Before Alfredo can connect to a remote repository, he needs to set up
+a way for his computer to authenticate with GitLab so it knows it’s him
+trying to connect to his remote repository.</p>
+<p>We are going to set up the method that is commonly used by many
+different services to authenticate access on the command line. This
+method is called Secure Shell Protocol (SSH). SSH is a cryptographic
+network protocol that allows secure communication between computers
+using an otherwise insecure network.</p>
+<p>SSH uses what is called a key pair. This is two keys that work
+together to validate access. One key is publicly known and called the
+public key, and the other key called the private key is kept private.
+Very descriptive names.</p>
+<p>You can think of the public key as a padlock, and only you have the
+key (the private key) to open it. You use the public key where you want
+a secure method of communication, such as your GitHub account. You give
+this padlock, or public key, to GitLab and say “lock the communications
+to my account with this so that only computers that have my private key
+can unlock communications and send git commands as my GitHub
+account.”</p>
+<p>What we will do now is the minimum required to set up the SSH keys
+and add the public key to a GitLab account.</p>
+<p>The first thing we are going to do is check if this has already been
+done on the computer you’re on. Because generally speaking, this setup
+only needs to happen once and then you can forget about it.</p>
+<div id="keeping-your-keys-secure" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="keeping-your-keys-secure" class="callout-inner">
+<h3 class="callout-title">Keeping your keys secure</h3>
+<div class="callout-content">
+<p>You shouldn’t really forget about your SSH keys, since they keep your
+account secure. It’s good practice to audit your secure shell keys every
+so often. Especially if you are using multiple computers to access your
+account.</p>
+</div>
+</div>
+</div>
+<p>We will run the list command to check what key pairs already exist on
+your computer.</p>
+<div class="codewrapper sourceCode" id="cb4">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" tabindex="-1"></a><span class="ex">$</span> ls <span class="at">-al</span> ~/.ssh</span></code></pre>
+</div>
+<p>Your output is going to look a little different depending on whether
+or not SSH has ever been set up on the computer you are using.</p>
+<p>Alfredo has not set up SSH on his computer, so his output is</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>ls: cannot access '/c/Users/Alfredo/.ssh': No such file or directory</code></pre>
+</div>
+<p>If SSH has been set up on the computer you’re using, the public and
+private key pairs will be listed. The file names are either
+<code>id_ed25519</code>/<code>id_ed25519.pub</code> or
+<code>id_rsa</code>/<code>id_rsa.pub</code> depending on how the key
+pairs were set up. Since they don’t exist on Alfredo’s computer, he uses
+this command to create them.</p>
+<div class="section level5">
+<h5 id="create-an-ssh-key-pair">Create an SSH key pair<a class="anchor" aria-label="anchor" href="#create-an-ssh-key-pair"></a></h5>
+<p>To create an SSH key pair Alfredo uses this command, where the
+<code>-t</code> option specifies which type of algorithm to use and
+<code>-C</code> attaches a comment to the key (here, Alfredo’s
+email):</p>
+<div class="codewrapper sourceCode" id="cb6">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" tabindex="-1"></a><span class="ex">$</span> ssh-keygen <span class="at">-t</span> ed25519 <span class="at">-C</span> <span class="st">"a.linguini@ratatouille.fr"</span></span></code></pre>
+</div>
+<p>If you are using a legacy system that doesn’t support the Ed25519
+algorithm, use:
+<code>$ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"</code></p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Generating public/private ed25519 key pair.
+Enter file in which to save the key (/c/Users/Alfredo/.ssh/id_ed25519):</code></pre>
+</div>
+<p>We want to use the default file, so just press <kbd>Enter</kbd>.</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Created directory '/c/Users/Alfredo/.ssh'.
+Enter passphrase (empty for no passphrase):</code></pre>
+</div>
+<p>Now, it is prompting Alfredo for a passphrase. Since he is using his
+kitchen’s laptop that other people sometimes have access to, he wants to
+create a passphrase. Be sure to use something memorable or save your
+passphrase somewhere, as there is no “reset my password” option. Note
+that, when typing a passphrase on a terminal, there won’t be any visual
+feedback of your typing. This is normal: your passphrase will be
+recorded even if you see nothing changing on your screen.</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Enter same passphrase again:</code></pre>
+</div>
+<p>After entering the same passphrase a second time, we receive the
+confirmation</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Your identification has been saved in /c/Users/Alfredo/.ssh/id_ed25519
+Your public key has been saved in /c/Users/Alfredo/.ssh/id_ed25519.pub
+The key fingerprint is:
+SHA256:SMSPIStNyA00KPxuYu94KpZgRAYjgt9g4BA4kFy3g1o a.linguini@ratatouille.fr
+The key's randomart image is:
++--[ED25519 256]--+
+|^B== o.          |
+|%*=.*.+          |
+|+=.E =.+         |
+| .=.+.o..        |
+|....  . S        |
+|.+ o             |
+|+ =              |
+|.o.o             |
+|oo+.             |
++----[SHA256]-----+</code></pre>
+</div>
+<p>The “identification” is actually the private key. You should never
+share it. The public key is appropriately named. The “key fingerprint”
+is a shorter version of a public key.</p>
+<p>Now that we have generated the SSH keys, we will find the SSH files
+when we check.</p>
+<div class="codewrapper sourceCode" id="cb11">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="fu">ls</span> <span class="at">-al</span> ~/.ssh</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>drwxr-xr-x 1 Alfredo   197121   0 Jul 16 14:48 ./
+drwxr-xr-x 1 Alfredo   197121   0 Jul 16 14:48 ../
+-rw-r--r-- 1 Alfredo   197121 419 Jul 16 14:48 id_ed25519
+-rw-r--r-- 1 Alfredo   197121 106 Jul 16 14:48 id_ed25519.pub</code></pre>
+</div>
+</div>
+<div class="section level5">
+<h5 id="copy-the-public-key-to-github">Copy the public key to GitHub<a class="anchor" aria-label="anchor" href="#copy-the-public-key-to-github"></a></h5>
+<p>Now we have a SSH key pair and we can run this command to check if
+GitHub can read our authentication.</p>
+<div class="codewrapper sourceCode" id="cb13">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="fu">ssh</span> <span class="at">-T</span> git@gitlab.tudelft.nl</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>The authenticity of host 'gitlab.tudelft.nl (192.30.255.112)' can't be established.
+RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
+This key is not known by any other names
+Are you sure you want to continue connecting (yes/no/[fingerprint])? y
+Please type 'yes', 'no' or the fingerprint: yes
+Warning: Permanently added 'gitlab.tudelft.nl' (RSA) to the list of known hosts.
+git@gitlab.tudelft.nl: Permission denied (publickey).</code></pre>
+</div>
+<p>Right, we forgot that we need to give GitLab our public key!</p>
+<p>First, we need to copy the public key. Be sure to include the
+<code>.pub</code> at the end, otherwise you’re looking at the private
+key.</p>
+<div class="codewrapper sourceCode" id="cb15">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="fu">cat</span> ~/.ssh/id_ed25519.pub</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDmRA3d51X0uu9wXek559gfn6UFNF69yZjChyBIU2qKI a.linguini@ratatouille.fr</code></pre>
+</div>
+<p>Now, going to the GitLab page in your browser, click on your profile
+icon in the top right corner of the left panel, then click on the
+<code>SSH Keys</code> link under <code>User Settings</code> in the same
+panel:</p>
+<figure><img src="../fig/gitlab_ssh_keys.jpg" alt="The SSH Keys page in GitLab" class="figure mx-auto d-block"></figure><p>Click on the <code>Add new key</code> button, which will take you to
+a page like this:</p>
+<figure><img src="../fig/gitlab_add_new_key.jpg" alt="Adding a new key in GitLab" class="figure mx-auto d-block"></figure><p>Here, you can paste your public key in the <code>Key</code> box, add
+a title, and set an expiration date. Once everything is filled in, you
+can click the <code>Add key</code> button.</p>
+<p>Now that we’ve set that up, let’s check our authentication again from
+the command line.</p>
+<div class="codewrapper sourceCode" id="cb17">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="ex">$</span> ssh <span class="at">-T</span> git@gitlab.tudelft.nl</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Welcome to GitLab, @alflin!</code></pre>
+</div>
+<p>Good! This output confirms that the SSH key works as intended. We are
+now ready to push our work to the remote repository.</p>
+</div>
+</div>
+<div class="section level3">
+<h3 id="push-local-changes-to-a-remote">Push local changes to a remote<a class="anchor" aria-label="anchor" href="#push-local-changes-to-a-remote"></a></h3>
+<p>Now that authentication is setup, we can return to the remote. This
+command will push the changes from our local repository to the
+repository on GitHub:</p>
+<div class="codewrapper sourceCode" id="cb19">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="ex">$</span> git push origin main</span></code></pre>
+</div>
+<p>Since Alfredo set up a passphrase, it will prompt him for it. If you
+completed advanced settings for your authentication, it will not prompt
+for a passphrase.</p>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>Enumerating objects: 16, done.
+Counting objects: 100% (16/16), done.
+Delta compression using up to 8 threads.
+Compressing objects: 100% (11/11), done.
+Writing objects: 100% (16/16), 1.45 KiB | 372.00 KiB/s, done.
+Total 16 (delta 2), reused 0 (delta 0)
+remote: Resolving deltas: 100% (2/2), done.
+To https://gitlab.tudelft.nl/alflin/recipes.git
+ * [new branch]      main -&gt; main</code></pre>
+</div>
+<div id="password-managers" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="password-managers" class="callout-inner">
+<h3 class="callout-title">Password Managers</h3>
+<div class="callout-content">
+<p>If your operating system has a password manager configured,
+<code>git push</code> will try to use it when it needs your username and
+password. For example, this is the default behavior for Git Bash on
+Windows. If you want to type your username and password at the terminal
+instead of using a password manager, type:</p>
+<div class="codewrapper sourceCode" id="cb21">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="ex">$</span> unset SSH_ASKPASS</span></code></pre>
+</div>
+<p>in the terminal, before you run <code>git push</code>. Despite the
+name, <a href="https://git-scm.com/docs/gitcredentials#_requesting_credentials" class="external-link">Git
+uses <code>SSH_ASKPASS</code> for all credential entry</a>, so you may
+want to unset <code>SSH_ASKPASS</code> whether you are using Git via SSH
+or https.</p>
+<p>You may also want to add <code>unset SSH_ASKPASS</code> at the end of
+your <code>~/.bashrc</code> to make Git default to using the terminal
+for usernames and passwords.</p>
+</div>
+</div>
+</div>
+<p>Our local and remote repositories are now in this state:</p>
+<figure><img src="../fig/github-repo-after-first-push.svg" alt="GitLab repo after first push" class="figure mx-auto d-block"></figure><p>We can pull changes from the remote repository to the local one as
+well:</p>
+<div class="codewrapper sourceCode" id="cb22">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="ex">$</span> git pull origin main</span></code></pre>
+</div>
+<div class="codewrapper">
+<h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="output" tabindex="0"><code>From https://gitlab.tudelft.nl/alflin/recipes
+ * branch            main     -&gt; FETCH_HEAD
+Already up-to-date.</code></pre>
+</div>
+<p>Pulling has no effect in this case because the two repositories are
+already synchronized. If someone else had pushed some changes to the
+repository on GitHub, though, this command would download them to our
+local repository.</p>
+</div>
 </section><section><h2 class="section-heading" id="adding-project-members">Adding Project Members<a class="anchor" aria-label="anchor" href="#adding-project-members"></a></h2>
 <hr class="half-width"><p>So far, each of you has created a GitLab project that no one but you
 can contribute to; depending on the visibility setting, no one but you
@@ -743,9 +1076,9 @@ <h3 class="callout-title">Key Points</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/gitlab.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/gitlab.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/images.html b/instructor/images.html
index 84b62cc..197cc4b 100644
--- a/instructor/images.html
+++ b/instructor/images.html
@@ -446,6 +446,24 @@ <h3 id="gitlab-figure-5">Figure 5</h3>
 <figure><img src="../fig/new-project.png" alt="Project homepage for a new project" class="figure mx-auto d-block"><div class="figcaption">Fresh project homepage</div>
 </figure><hr>
 <h3 id="gitlab-figure-6">Figure 6</h3>
+<p aria-hidden="true">Image 1 of 1: ‘Local repository with staging area’</p>
+<figure><img src="../fig/git-staging-area.svg" alt="Local repository with staging area" class="figure mx-auto d-block"></figure><hr>
+<h3 id="gitlab-figure-7">Figure 7</h3>
+<p aria-hidden="true">Image 1 of 1: ‘The local and remote Git repos’</p>
+<figure><img src="../fig/git-freshly-made-gitlab-repo.svg" alt="The local and remote Git repos" class="figure mx-auto d-block"></figure><hr>
+<h3 id="gitlab-figure-8">Figure 8</h3>
+<p aria-hidden="true">Image 1 of 1: ‘Accessing a GitLab repo via SSH’</p>
+<figure><img src="../fig/gitlab_ssh_repo.jpg" alt="Accessing a GitLab repo via SSH" class="figure mx-auto d-block"></figure><hr>
+<h3 id="gitlab-figure-9">Figure 9</h3>
+<p aria-hidden="true">Image 1 of 1: ‘The SSH Keys page in GitLab’</p>
+<figure><img src="../fig/gitlab_ssh_keys.jpg" alt="The SSH Keys page in GitLab" class="figure mx-auto d-block"></figure><hr>
+<h3 id="gitlab-figure-10">Figure 10</h3>
+<p aria-hidden="true">Image 1 of 1: ‘Adding a new key in GitLab’</p>
+<figure><img src="../fig/gitlab_add_new_key.jpg" alt="Adding a new key in GitLab" class="figure mx-auto d-block"></figure><hr>
+<h3 id="gitlab-figure-11">Figure 11</h3>
+<p aria-hidden="true">Image 1 of 1: ‘GitLab repo after first push’</p>
+<figure><img src="../fig/github-repo-after-first-push.svg" alt="GitLab repo after first push" class="figure mx-auto d-block"></figure><hr>
+<h3 id="gitlab-figure-12">Figure 12</h3>
 <p aria-hidden="true">Image 1 of 1: ‘Project Members page’</p>
 <figure><img src="../fig/initial-members.png" alt="Project Members page" class="figure mx-auto d-block"><div class="figcaption">Project members page</div>
 </figure><hr></section><section id="advanced-git-commands"><h2 class="section-heading"><a href="advanced-git-commands.html">Advanced Git Commands</a></h2>
@@ -532,6 +550,9 @@ <h3 id="clean-code-figure-2">Figure 2</h3>
 <figure><img src="../fig/clean_code.png" alt="How to measure clean code?" class="figure mx-auto d-block"></figure><hr>
 <h3 id="clean-code-figure-3">Figure 3</h3>
 <p aria-hidden="true">Image 1 of 1: ‘Running Pytest from PyCharm’</p>
+<figure><img src="../fig/pycharm_python_interpreter.jpg" alt="Running Pytest from PyCharm" class="figure mx-auto d-block"></figure><hr>
+<h3 id="clean-code-figure-4">Figure 4</h3>
+<p aria-hidden="true">Image 1 of 1: ‘Running Pytest from PyCharm’</p>
 <figure><img src="../fig/pytest_pycharm.jpg" alt="Running Pytest from PyCharm" class="figure mx-auto d-block"></figure><hr></section><section id="credits"><h2 class="section-heading"><a href="credits.html">Credits</a></h2>
 <hr class="half-width"></section>
 </div>
@@ -580,9 +601,9 @@ <h3 id="clean-code-figure-3">Figure 3</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/images.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/images.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/index.html b/instructor/index.html
index 15832ba..bcfe7ec 100644
--- a/instructor/index.html
+++ b/instructor/index.html
@@ -530,9 +530,9 @@ <h2 class="accordion-header" id="flush-headingTwelve">
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/index.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/index.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/instructor-notes.html b/instructor/instructor-notes.html
index f1f5404..4953b8f 100644
--- a/instructor/instructor-notes.html
+++ b/instructor/instructor-notes.html
@@ -455,9 +455,9 @@ <h1>Instructor Notes</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/instructor-notes.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/instructor-notes.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/key-points.html b/instructor/key-points.html
index e00a0ff..3db0bcc 100644
--- a/instructor/key-points.html
+++ b/instructor/key-points.html
@@ -538,9 +538,9 @@ <h2 class="accordion-header" id="flush-headingTwelve">
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/key-points.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/key-points.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/profiles.html b/instructor/profiles.html
index 0e810e5..e53c9ce 100644
--- a/instructor/profiles.html
+++ b/instructor/profiles.html
@@ -369,9 +369,9 @@ <h1>Learner Profiles</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/profiles.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/profiles.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/python-virtual-environmants.html b/instructor/python-virtual-environmants.html
index 8cfcc9a..b8327c6 100644
--- a/instructor/python-virtual-environmants.html
+++ b/instructor/python-virtual-environmants.html
@@ -1078,9 +1078,9 @@ <h3 class="callout-title">Key Points</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/python-virtual-environmants.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/python-virtual-environmants.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-12-03",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/qsmm.html b/instructor/qsmm.html
index 01827c3..0e32e66 100644
--- a/instructor/qsmm.html
+++ b/instructor/qsmm.html
@@ -565,9 +565,9 @@ <h3 class="callout-title">Group exercise</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/qsmm.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/qsmm.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-12-09",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/reference.html b/instructor/reference.html
index 3ee9b53..5b71d24 100644
--- a/instructor/reference.html
+++ b/instructor/reference.html
@@ -507,9 +507,9 @@ <h1>Git Cheatsheets for Quick Reference</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/reference.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/reference.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-11-18",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/instructor/version_control.html b/instructor/version_control.html
index fbd9b7f..e6632c2 100644
--- a/instructor/version_control.html
+++ b/instructor/version_control.html
@@ -1162,9 +1162,9 @@ <h3 class="callout-title">Key Points</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/version_control.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/instructor/version_control.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-12-12",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/key-points.html b/key-points.html
index f7cf109..bab4c40 100644
--- a/key-points.html
+++ b/key-points.html
@@ -536,9 +536,9 @@ <h2 class="accordion-header" id="flush-headingTwelve">
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/key-points.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/key-points.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/md5sum.txt b/md5sum.txt
index 75da1c8..c0b4ebb 100644
--- a/md5sum.txt
+++ b/md5sum.txt
@@ -7,10 +7,10 @@
 "episodes/qsmm.Rmd" "e49596d65768b0880d2e011890f2e856" "site/built/qsmm.md" "2024-12-09"
 "episodes/version_control.Rmd" "795b029dfc310a59c4958ceba768b1f4" "site/built/version_control.md" "2024-12-12"
 "episodes/basic-git-commands.Rmd" "e0d7cd08985c490c0a2fe672cf8516fd" "site/built/basic-git-commands.md" "2024-12-03"
-"episodes/gitlab.Rmd" "b397c31571390eafaaf9bf8548ecd255" "site/built/gitlab.md" "2024-12-17"
+"episodes/gitlab.Rmd" "9a9a4e6d08a3f0f1e4a9193f0514a84d" "site/built/gitlab.md" "2024-12-19"
 "episodes/advanced-git-commands.Rmd" "cd7b1a79a0df91f57da82c654ef38190" "site/built/advanced-git-commands.md" "2024-12-12"
 "episodes/python-virtual-environmants.Rmd" "c5d13a03fc4109952fc33471e81848cf" "site/built/python-virtual-environmants.md" "2024-12-03"
-"episodes/clean-code.Rmd" "941d53ca0298605671b9de3db8c20cdd" "site/built/clean-code.md" "2024-12-17"
+"episodes/clean-code.Rmd" "788e59da90219aaf9bcdd78c67210068" "site/built/clean-code.md" "2024-12-19"
 "episodes/credits.Rmd" "9552b243be9586ef9ea63e330a838c06" "site/built/credits.md" "2024-12-04"
 "instructors/instructor-notes.md" "cae72b6712578d74a49fea7513099f8c" "site/built/instructor-notes.md" "2024-11-18"
 "learners/reference.md" "29355215471e0f912ffdcea5f2e26f3c" "site/built/reference.md" "2024-11-18"
diff --git a/pkgdown.yml b/pkgdown.yml
index ef1f5a8..d8f29fb 100644
--- a/pkgdown.yml
+++ b/pkgdown.yml
@@ -2,4 +2,4 @@ pandoc: 3.1.11
 pkgdown: 2.1.1
 pkgdown_sha: ~
 articles: {}
-last_built: 2024-12-17T15:12Z
+last_built: 2024-12-19T07:52Z
diff --git a/profiles.html b/profiles.html
index 21ef35e..5f50c94 100644
--- a/profiles.html
+++ b/profiles.html
@@ -369,9 +369,9 @@ <h1>Learner Profiles</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/profiles.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/profiles.html",
-  "dateCreated": "2024-12-17",
-  "dateModified": "2024-12-17",
-  "datePublished": "2024-12-17"
+  "dateCreated": "2024-12-19",
+  "dateModified": "2024-12-19",
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/python-virtual-environmants.html b/python-virtual-environmants.html
index 1a42f6c..92563b1 100644
--- a/python-virtual-environmants.html
+++ b/python-virtual-environmants.html
@@ -1076,9 +1076,9 @@ <h3 class="callout-title">Key Points</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/python-virtual-environmants.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/python-virtual-environmants.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-12-03",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/qsmm.html b/qsmm.html
index 2eb81b8..553743e 100644
--- a/qsmm.html
+++ b/qsmm.html
@@ -563,9 +563,9 @@ <h3 class="callout-title">Group exercise</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/qsmm.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/qsmm.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-12-09",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/reference.html b/reference.html
index 6628bab..96362a3 100644
--- a/reference.html
+++ b/reference.html
@@ -505,9 +505,9 @@ <h1>Git Cheatsheets for Quick Reference</h1>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/reference.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/reference.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-11-18",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>
diff --git a/version_control.html b/version_control.html
index 19911a9..2e0266a 100644
--- a/version_control.html
+++ b/version_control.html
@@ -1160,9 +1160,9 @@ <h3 class="callout-title">Key Points</h3>
   "creativeWorkStatus": "active",
   "url": "https://QuTech-Delft.github.io/prosoftdev-research/version_control.html",
   "identifier": "https://QuTech-Delft.github.io/prosoftdev-research/version_control.html",
-  "dateCreated": "2024-12-17",
+  "dateCreated": "2024-12-19",
   "dateModified": "2024-12-12",
-  "datePublished": "2024-12-17"
+  "datePublished": "2024-12-19"
 }
 
   </script><script>