Test workflow

Author: mendax1234

.github/workflows/update-submodule.yml

@@ -15,39 +15,25 @@ jobs:
       uses: actions/checkout@v3
       with:
         submodules: 'recursive'  # Ensure submodules are checked out
+        fetch-depth: 0  # Fetch full history to ensure we can pull latest commits
 
-    # Step 2: Reset submodule to the latest commit
-    - name: Reset submodule to latest commit
+    # Step 2: Update submodules to their latest main branch commits
+    - name: Update submodules
       run: |
-        # Reinitialize the submodule (resets its state)
+        # Initialize and update all submodules to their latest commits on main
         git submodule update --init --recursive
-        git submodule foreach 'git reset --hard origin/main'  # This resets the submodule to the latest commit from remote
+        git submodule foreach 'git fetch origin main:main && git checkout main && git pull origin main'
 
-    # Step 3: Check if the submodule is already up-to-date
+    # Step 3: Check if submodules have changed
     - name: Check submodule status
       id: submodule-status
       run: |
-        # Fetch the current commit of the submodule
-        CURRENT_COMMIT=$(git submodule status --recursive | awk '{ print $1 }')
-        
-        # Ensure we're working with the latest submodule state
-        git submodule update --init --recursive  # Initialize or update submodule to ensure it's in sync
-        
-        # Go to the submodule directory and fetch the latest commits from the remote repository
-        cd path/to/submodule  # Ensure you replace this with the actual submodule path
-        git fetch origin  # Fetch the latest changes from the remote
-        git checkout main  # Ensure we're on the main branch (or whichever branch you want)
-        git pull origin main  # Pull the latest changes from the remote
-
-        # Get the latest commit hash after the update
-        LATEST_COMMIT=$(git rev-parse HEAD)
-
-        # Check if the submodule commit has changed
-        if [ "$CURRENT_COMMIT" != "$LATEST_COMMIT" ]; then
-          echo "Submodule updated."
+        # Check if there are any changes in submodules
+        if [[ -n "$(git status --porcelain)" ]]; then
+          echo "Submodules have been updated."
           echo "submodule_updated=true" >> $GITHUB_ENV
         else
-          echo "No submodule update needed."
+          echo "No submodule updates needed."
           echo "submodule_updated=false" >> $GITHUB_ENV
         fi
 
@@ -58,12 +44,12 @@ jobs:
         git config --global user.name "github-actions[bot]"
         git config --global user.email "github-actions[bot]@users.noreply.github.com"
         git add .
-        git commit -m "CI: Update submodules" || echo "No changes to commit"
+        git commit -m "CI: Update submodules to latest main branch commits" || echo "No changes to commit"
 
     # Step 5: Pull the latest changes from the remote branch before pushing
     - name: Pull the latest changes
       if: env.submodule_updated == 'true'
-      run: git pull origin main --rebase --allow-unrelated-histories
+      run: git pull origin ${{ github.ref_name }} --rebase --allow-unrelated-histories
 
     # Step 6: Push the changes back to the repository
     - name: Push changes
@@ -72,4 +58,4 @@ jobs:
         TOKEN: ${{ secrets.PAT_TOKEN }}
       run: |
         git remote set-url origin https://x-access-token:${TOKEN}@github.com/${{ github.repository }}.git
-        git push origin HEAD
+        git push origin HEAD

README.md

@@ -2,86 +2,57 @@
 
 Welcome to my **Lecture Notes**! This repository contains carefully curated and organized notes from my studies at the National University of Singapore (NUS), focusing primarily on **Computer Engineering** and related topics. These notes are designed to serve as a study aid and reference for both myself and others who might find them useful.
 
----
-
 ## 📚 **Contents**
-
 The repository is organized into the following sections:
-
 - **Semester-wise Notes**  
   Notes are categorized based on academic semesters, making it easy to track progress over time.
-
 - **Subject-wise Topics**  
   Within each semester folder, notes are further divided by subject and module codes for clarity.
-
 - **Additional Resources**  
   Includes summaries, cheat sheets, and references to external resources when applicable.
 
----
-
 ## 🔖 **Features**
-
 - **Structured Format**  
   Notes are organized in a clean and consistent style:  
   - **Technical Subjects**: Written in Markdown and deployed via GitBook for easy navigation and accessibility.  
   - **Math and Physics**: Written in LaTeX and compiled using Overleaf to maintain precision and clarity.  
-
 - **Rich Content**  
   Includes detailed explanations, examples, diagrams, and code snippets where applicable.
-
 - **Cross-References**  
   Links to related topics or prerequisite material are provided for a seamless learning experience.
-
 - **Version Controlled**  
   Changes and improvements to the notes are tracked using Git, ensuring the latest updates are always available.
 
----
-
 ## 🛠 **Setup**
-
 To view and use these notes:
-
 1. **Clone the Repository**  
    Download the repository to your local machine:  
    ```bash
    git clone https://github.com/mendax1234/lecture-notes.git
    cd lecture-notes
    ```
-
 2. **Markdown Notes**  
    - Open Markdown files using any Markdown viewer or IDE (e.g., VS Code, Obsidian).  
-
 3. **LaTeX Notes**  
    - For LaTeX notes, upload the `.tex` files to [Overleaf](https://www.overleaf.com/) or use a local LaTeX editor (e.g., TeXShop, MikTeX).  
    - Compile the `.tex` files to generate PDFs for an optimal reading experience.
-
 4. **Navigation**  
    Browse through the folders to find the specific notes you need. Notes are organized by semesters, subjects, and topics for easy access.
 
----
-
 ## 📝 **Contribution Guidelines**
-
 Your contributions are welcome! To contribute:
-
 1. Fork this repository.
 2. Make edits or add new notes in a **relevant folder**.
 3. Submit a pull request with a clear description of your changes.
 
 Please ensure that your notes follow the existing structure and maintain clarity and conciseness.
 
----
 
 ## 🙌 **Acknowledgments**
-
 A huge thank you to the professors, teaching assistants, and peers at NUS who have contributed to my understanding of these subjects. This repository reflects the collective effort of countless hours of lectures, discussions, and study sessions.
 
----
 
 ## 📨 **Feedback and Contact**
-
 If you have any feedback, suggestions, or questions, feel free to open an issue or contact me directly via GitHub. Let’s learn and grow together!  
 
----
-
 Hope you find these notes helpful in your learning journey. 😊