From 16edfe9c8a7ec8c8dc6966c532bac4668755c9c0 Mon Sep 17 00:00:00 2001
From: Alexi Gladstone <alexigladstone@gmail.com>
Date: Tue, 28 Jan 2025 12:08:15 -0500
Subject: [PATCH 1/4] Add my website to readme under
 academics--alexiglad.github.io (#2987)

---
 README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/README.md b/README.md
index f11f438a686e..0e8473fc213d 100644
--- a/README.md
+++ b/README.md
@@ -159,6 +159,7 @@ Feel free to add your own page(s) by sending a PR.
 <a href="https://vmooers.github.io/" target="_blank">★</a>
 <a href="https://jpfonseca.github.io/" target="_blank">★</a>
 <a href="https://dmitryryumin.github.io/" target="_blank">★</a>
+<a href="https://alexiglad.github.io/" target="_blank">★</a>
 </td>
 </tr>
 <tr>

From caf9976175684ff8c9df6859ea192350df1e9ce1 Mon Sep 17 00:00:00 2001
From: George <31376482+george-gca@users.noreply.github.com>
Date: Thu, 30 Jan 2025 16:02:39 -0300
Subject: [PATCH 2/4] Add link to set workflow permissions

---
 INSTALL.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/INSTALL.md b/INSTALL.md
index e4279273ef53..03b7f8f93eec 100644
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -24,7 +24,7 @@
 The recommended approach for using **al-folio** is to first create your own site using the template with as few changes as possible, and only when it is up and running customize it however you like. This way it is easier to pinpoint what causes a potential issue in case of a bug. The minimum steps required to create your own site are ([video tutorial here](assets/video/tutorial_al_folio.mp4)):
 
 1. Create a new repository using this template. For this, click on [Use this template -> Create a new repository](https://github.com/new?template_name=al-folio&template_owner=alshedivat) above the file list. If you plan to upload your site to `<your-github-username>.github.io`, note that the name of your repository :warning: **MUST BE** :warning: `<your-github-username>.github.io` or `<your-github-orgname>.github.io`, as stated in the [GitHub pages docs](https://docs.github.com/en/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites).
-2. In this new repository, go to `Settings -> Actions -> General -> Workflow permissions` and give `Read and write permissions` to GitHub Actions.
+2. In this new repository, go to [Settings -> Actions -> General -> Workflow permissions](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-default-github_token-permissions) and give `Read and write permissions` to GitHub Actions.
 3. Open file `_config.yml`, set `url` to `https://<your-github-username>.github.io` and leave `baseurl` **empty** (do NOT delete it), as `baseurl:`.
 4. Wait until the GitHub action with subtitle `Deploy site` finishes (check your repository **Actions** tab), which takes ~4 min. Now, in addition to the `main` branch, your repository has a newly built `gh-pages` branch.
 5. Finally, in the repository page go to `Settings -> Pages -> Build and deployment`, make sure that `Source` is set to `Deploy from a branch` and set the branch to `gh-pages` (NOT to main).

From beeff21ecdca68b0d650cdcf0b1b3af3fe7ff483 Mon Sep 17 00:00:00 2001
From: Soumyaranjan Dash <51014191+sr-dash@users.noreply.github.com>
Date: Sun, 9 Feb 2025 04:41:20 -1000
Subject: [PATCH 3/4] Updated scripts for correctly using gtag. (#2962)

Implementation of Google tag ID to correctly getting tracked requires
further modification in addition to the one line script in the
`_includes/scripts.liquid` file as
```
<script async src="https://www.googletagmanager.com/gtag/js?id={{ site.google_analytics }}"></script>
  <script>
    window.dataLayer = window.dataLayer || [];
    function gtag() {
      dataLayer.push(arguments);
    }
    gtag('js', new Date());

    gtag('config', '{{ site.google_analytics }}');
  </script>
```

I have made the changes and tested it out on my personal webpage to
ensure the tracking in analytics dashboard.
---
 _includes/scripts.liquid | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/_includes/scripts.liquid b/_includes/scripts.liquid
index 7bbd07166933..402eafdae9df 100644
--- a/_includes/scripts.liquid
+++ b/_includes/scripts.liquid
@@ -216,6 +216,15 @@
   <!-- Analytics -->
   <!-- Global site tag (gtag.js) - Google Analytics -->
   <script async src="https://www.googletagmanager.com/gtag/js?id={{ site.google_analytics }}"></script>
+  <script>
+    window.dataLayer = window.dataLayer || [];
+    function gtag() {
+      dataLayer.push(arguments);
+    }
+    gtag('js', new Date());
+
+    gtag('config', '{{ site.google_analytics }}');
+  </script>
   <script defer src="{{ '/assets/js/google-analytics-setup.js' | relative_url | bust_file_cache }}"></script>
 {% endif %}
 

From e3f029dcd111c45eb1ea82b1108b3798fbf61abb Mon Sep 17 00:00:00 2001
From: George <31376482+george-gca@users.noreply.github.com>
Date: Sun, 9 Feb 2025 12:21:55 -0300
Subject: [PATCH 4/4] Added sass changes to trigger deploy action

---
 .github/workflows/deploy.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
index 1f1fc63b111d..7046747242dc 100644
--- a/.github/workflows/deploy.yml
+++ b/.github/workflows/deploy.yml
@@ -7,6 +7,7 @@ on:
       - main
     paths:
       - "assets/**"
+      - "_sass/**"
       - "**.bib"
       - "**.html"
       - "**.js"
@@ -34,6 +35,7 @@ on:
       - main
     paths:
       - "assets/**"
+      - "_sass/**"
       - "**.bib"
       - "**.html"
       - "**.js"