From bd86f4fc950cdc5bb4cb346f48c14a6e356dc4fb Mon Sep 17 00:00:00 2001
From: David Luevano Alvarado <david@luevano.xyz>
Date: Thu, 7 Mar 2024 21:55:16 -0600
Subject: stop tracking live/

---
 .../fork-awesome/src/doc/_includes/new-upgrading.html       | 13 -------------
 1 file changed, 13 deletions(-)
 delete mode 100644 live/static/fork-awesome/src/doc/_includes/new-upgrading.html

(limited to 'live/static/fork-awesome/src/doc/_includes/new-upgrading.html')

diff --git a/live/static/fork-awesome/src/doc/_includes/new-upgrading.html b/live/static/fork-awesome/src/doc/_includes/new-upgrading.html
deleted file mode 100644
index 0bcabc3..0000000
--- a/live/static/fork-awesome/src/doc/_includes/new-upgrading.html
+++ /dev/null
@@ -1,13 +0,0 @@
-<section id="new-upgrading">
-  <h2 class="page-header">Switching from {{ site.fontawesome.name }} {{ site.fontawesome.minor_version }}?</h2>
-  <p>
-    If you were using {{ site.fontawesome.name }} {{ site.fontawesome.minor_version }}, you should be able to just switch to {{ site.forkawesome.name }} {{ site.forkawesome.minor_version }} and get all the benefits from it.
-    If you were using npm or composer packages, replace the ones you were using by this {{ site.forkawesome.name }} ones. Or if you downloaded a static copy of {{ site.fontawesome.name }}, download the latest version of {{ site.forkawesome.name }} and
-    replace CSS and font files in your project and you should be good to go.
-  </p>
-  <p>
-    We paid special attention not to change unicode codepoints for the existing icons, nor changed the CSS class names or icon names from {{ site.fontawesome.name }} {{ site.fontawesome.minor_version }}.
-    Though we added a few more icons and made the process of contributing to this project much easier.
-    Though, if you see a mistake, please don't hesitate to <a href="{{ page.relative_path }}community/#reporting-bugs">file a bug</a>.
-  </p>
-</section>
-- 
cgit v1.2.3-54-g00ecf