From cd517d9fabea502d8f0c3330ede629a25e27a6a7 Mon Sep 17 00:00:00 2001
From: Karthick Jayaraman <99075859+Karthick-840@users.noreply.github.com>
Date: Sun, 7 Apr 2024 21:51:59 +0200
Subject: [PATCH] Update README.md

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

diff --git a/README.md b/README.md
index 7736cd1..cd249f7 100644
--- a/README.md
+++ b/README.md
@@ -29,3 +29,4 @@ See more info at https://academicpages.github.io/
 There is one logistical issue with a ready-to-fork template theme like academic pages that makes it a little tricky to get bug fixes and updates to the core theme. If you fork this repository, customize it, then pull again, you'll probably get merge conflicts. If you want to save your various .yml configuration files and markdown files, you can delete the repository and fork it again. Or you can manually patch. 
 
 To support this, all changes to the underlying code appear as a closed issue with the tag 'code change' -- get the list [here](https://github.com/academicpages/academicpages.github.io/issues?q=is%3Aclosed%20is%3Aissue%20label%3A%22code%20change%22%20). Each issue thread includes a comment linking to the single commit or a diff across multiple commits, so those with forked repositories can easily identify what they need to patch.
+Changing for deployment