Merged
Conversation
|
@UjwalYdv is attempting to deploy a commit to the RAJ ROY's projects Team on Vercel. A member of the Team first needs to authorize it. |
📝 WalkthroughWalkthroughThis PR removes unused dayjs plugin dependencies from the Vite build cache and updates its metadata hashes. It concurrently adds comprehensive documentation pages for electrical engineering courses (EE201–EE205) and updates semester-level resource hubs (SEM3 and SEM4) with structured course information, resource links, and contribution guidelines. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 8
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@branch/electrical/SEM3/EE201/index.md`:
- Around line 49-64: Update the example contributor listing and naming
conventions to reference EE201 instead of CE102 and mark the fenced code block
as text: change the block fence from ``` to ```text, replace the directory and
filenames (CE102/... → EE201/ and CE102_* → EE201_*), and update the three
naming convention examples (CE102_Mid_YYYY, CE102_Lecture#, CE102_Assignment#)
to use EE201_Mid_YYYY, EE201_Lecture#, and EE201_Assignment# so the page content
and markdownlint language tag are consistent with EE201.
In `@branch/electrical/SEM3/EE202/index.md`:
- Around line 49-64: Update the contributing example block and naming
conventions to reference the correct course code and fence language: replace all
occurrences of "CE102" with "EE202" inside the code fence and in the three
naming-convention examples (exams, notes, assignments), and change the fenced
block language from ``` to ```text so the snippet shows as plain text; target
the code sample under the "Option B: Add Drive Links (Recommended)" section and
the three bullet lines beginning with "For exams:", "For notes:", and "For
assignments:" to make the page course-accurate.
In `@branch/electrical/SEM3/EE203/index.md`:
- Around line 53-68: The snippet shows CE102 examples and an untyped code fence;
update the fenced example in index.md to use a language tag of "text" (change
``` to ```text) and replace all CE102-specific folder and filename examples and
naming convention lines with EE203 (or a generic <COURSE_CODE>) so contributors
follow the EE203 pattern—specifically modify the block that lists the folder
(CE102/ and CE102_* filenames) and the three naming convention bullets (exams,
notes, assignments) to use EE203_* equivalents and ensure the fence is closed
with ``` as ```text.
In `@branch/electrical/SEM3/EE204/index.md`:
- Around line 48-63: The contributing guide erroneously uses the CE102 course
code and a plain fenced block; update the sample tree and naming examples to use
the correct course code "EE204" everywhere (change instances of "CE102" in the
fenced block and the three naming convention lines to "EE204") and mark the
fenced block as text by adding the language tag (replace the opening ``` with
```text) so the snippet and naming convention align with EE204.
In `@branch/electrical/SEM3/EE205/index.md`:
- Around line 48-63: Update the README example block and naming conventions to
match EE205: change the fenced code block to declare a language (e.g., ```text)
and replace all CE102 examples with EE205 (or a <COURSE_CODE> placeholder) so
the tree and subsequent naming bullets use EE205 consistently; edit the fenced
block and the three bullets referencing exams/notes/assignments near the "Option
B: Add Drive Links (Recommended)" section to reflect this.
In `@branch/electrical/SEM3/index.md`:
- Around line 26-36: The quick-nav links use fragments like "#📚-subjects",
"#🧪-labs" and "#📖-pyqs" which likely don't match the markdown-generated
heading IDs; update the anchors so they match the actual slugified heading IDs
or add explicit HTML id attributes on the target headings (e.g., give the "📚
Subjects", "🧪 Labs" and "📖 PYQs" headings explicit ids and then change the
hrefs to those ids), and apply the same correction for the similar anchor at the
other occurrence (the one referenced at line 119).
In `@branch/electrical/SEM4/index.md`:
- Around line 26-36: The in-page quick-nav links use emoji-based fragment IDs
("#📚-subjects", "#🧪-labs", "#📖-pyqs") which are unstable; change these hrefs
to match the actual heading IDs (e.g., "#subjects", "#labs", "#pyqs") or add
explicit id attributes on the corresponding headings so they resolve reliably,
and update the anchor targets in the index.md card block that contains the three
links to use those stable ids.
- Line 48: The subtitle text currently reads "_Core SEM 3 curriculum — Click to
explore_" and should be updated to reflect this is the SEM4 hub; locate that
string in index.md and change "SEM 3" to "SEM 4" so it reads "_Core SEM 4
curriculum — Click to explore_"; verify there are no other occurrences of "SEM
3" on the page and update any remaining mismatched semester labels to "SEM 4".
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: bb38731d-6191-4f99-aae2-9c9a217484b3
⛔ Files ignored due to path filters (7)
.DS_Storeis excluded by!**/.DS_Store.vitepress/cache/deps/chunk-QNAROPK2.js.mapis excluded by!**/*.map.vitepress/cache/deps/dayjs_plugin_advancedFormat__js.js.mapis excluded by!**/*.map.vitepress/cache/deps/dayjs_plugin_customParseFormat__js.js.mapis excluded by!**/*.map.vitepress/cache/deps/dayjs_plugin_isoWeek__js.js.mapis excluded by!**/*.map.vitepress/dist/.DS_Storeis excluded by!**/dist/**,!**/.DS_Storepackage-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (22)
.vitepress/cache/deps/_metadata.json.vitepress/cache/deps/chunk-QNAROPK2.js.vitepress/cache/deps/dayjs_plugin_advancedFormat__js.js.vitepress/cache/deps/dayjs_plugin_customParseFormat__js.js.vitepress/cache/deps/dayjs_plugin_isoWeek__js.jsbranch/electrical/SEM3/EE201/PYQ/End-Semester/index.mdbranch/electrical/SEM3/EE201/PYQ/Mid-Semester/index.mdbranch/electrical/SEM3/EE201/index.mdbranch/electrical/SEM3/EE202/PYQ/End-Semester/index.mdbranch/electrical/SEM3/EE202/PYQ/Mid-Semester/index.mdbranch/electrical/SEM3/EE202/index.mdbranch/electrical/SEM3/EE203/PYQ/End-Semester/index.mdbranch/electrical/SEM3/EE203/PYQ/Mid-Semester/index.mdbranch/electrical/SEM3/EE203/index.mdbranch/electrical/SEM3/EE204/PYQ/End-Semester/index.mdbranch/electrical/SEM3/EE204/PYQ/Mid-Semester/index.mdbranch/electrical/SEM3/EE204/index.mdbranch/electrical/SEM3/EE205/PYQ/End-Semester/index.mdbranch/electrical/SEM3/EE205/PYQ/Mid-Semester/index.mdbranch/electrical/SEM3/EE205/index.mdbranch/electrical/SEM3/index.mdbranch/electrical/SEM4/index.md
💤 Files with no reviewable changes (4)
- .vitepress/cache/deps/dayjs_plugin_advancedFormat__js.js
- .vitepress/cache/deps/dayjs_plugin_customParseFormat__js.js
- .vitepress/cache/deps/chunk-QNAROPK2.js
- .vitepress/cache/deps/dayjs_plugin_isoWeek__js.js
Comment on lines
+49
to
+64
| ``` | ||
| CE102/ | ||
| ├── CE102_Mid_2024.pdf | ||
| ├── CE102_End_2023.pdf | ||
| └── CE102_Notes_TopicX.pdf | ||
| ``` | ||
|
|
||
| ### Option B: Add Drive Links (Recommended) | ||
|
|
||
| Add your Google Drive share link to the table above following the existing format. | ||
|
|
||
| **📝 Naming Convention** | ||
|
|
||
| - For exams: `CE102_Mid_YYYY.pdf` or `CE102_End_YYYY.pdf` | ||
| - For notes: `CE102_Lecture#_Topic.pdf` | ||
| - For assignments: `CE102_Assignment#_YYYY.pdf` |
There was a problem hiding this comment.
Update the contributor example to EE201.
Right now the example still uses CE102, which is confusing on an EE201 page, and the fenced block should be marked as text to satisfy markdownlint.
Suggested fix
-```
-CE102/
-├── CE102_Mid_2024.pdf
-├── CE102_End_2023.pdf
-└── CE102_Notes_TopicX.pdf
-```
+```text
+EE201/
+├── EE201_Mid_2024.pdf
+├── EE201_End_2023.pdf
+└── EE201_Notes_TopicX.pdf
+```
-- For exams: `CE102_Mid_YYYY.pdf` or `CE102_End_YYYY.pdf`
-- For notes: `CE102_Lecture#_Topic.pdf`
-- For assignments: `CE102_Assignment#_YYYY.pdf`
+- For exams: `EE201_Mid_YYYY.pdf` or `EE201_End_YYYY.pdf`
+- For notes: `EE201_Lecture#_Topic.pdf`
+- For assignments: `EE201_Assignment#_YYYY.pdf`📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ``` | |
| CE102/ | |
| ├── CE102_Mid_2024.pdf | |
| ├── CE102_End_2023.pdf | |
| └── CE102_Notes_TopicX.pdf | |
| ``` | |
| ### Option B: Add Drive Links (Recommended) | |
| Add your Google Drive share link to the table above following the existing format. | |
| **📝 Naming Convention** | |
| - For exams: `CE102_Mid_YYYY.pdf` or `CE102_End_YYYY.pdf` | |
| - For notes: `CE102_Lecture#_Topic.pdf` | |
| - For assignments: `CE102_Assignment#_YYYY.pdf` |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@branch/electrical/SEM3/EE201/index.md` around lines 49 - 64, Update the
example contributor listing and naming conventions to reference EE201 instead of
CE102 and mark the fenced code block as text: change the block fence from ``` to
```text, replace the directory and filenames (CE102/... → EE201/ and CE102_* →
EE201_*), and update the three naming convention examples (CE102_Mid_YYYY,
CE102_Lecture#, CE102_Assignment#) to use EE201_Mid_YYYY, EE201_Lecture#, and
EE201_Assignment# so the page content and markdownlint language tag are
consistent with EE201.
Comment on lines
+49
to
+64
| ``` | ||
| CE102/ | ||
| ├── CE102_Mid_2024.pdf | ||
| ├── CE102_End_2023.pdf | ||
| └── CE102_Notes_TopicX.pdf | ||
| ``` | ||
|
|
||
| ### Option B: Add Drive Links (Recommended) | ||
|
|
||
| Add your Google Drive share link to the table above following the existing format. | ||
|
|
||
| **📝 Naming Convention** | ||
|
|
||
| - For exams: `CE102_Mid_YYYY.pdf` or `CE102_End_YYYY.pdf` | ||
| - For notes: `CE102_Lecture#_Topic.pdf` | ||
| - For assignments: `CE102_Assignment#_YYYY.pdf` |
There was a problem hiding this comment.
Make the contributing section course-accurate.
This page is for EE202, but the example still uses CE102. That is easy for contributors to copy verbatim into the wrong folder/prefix. The fence should also be typed as text.
Suggested fix
-```
-CE102/
-├── CE102_Mid_2024.pdf
-├── CE102_End_2023.pdf
-└── CE102_Notes_TopicX.pdf
-```
+```text
+EE202/
+├── EE202_Mid_2024.pdf
+├── EE202_End_2023.pdf
+└── EE202_Notes_TopicX.pdf
+```
-- For exams: `CE102_Mid_YYYY.pdf` or `CE102_End_YYYY.pdf`
-- For notes: `CE102_Lecture#_Topic.pdf`
-- For assignments: `CE102_Assignment#_YYYY.pdf`
+- For exams: `EE202_Mid_YYYY.pdf` or `EE202_End_YYYY.pdf`
+- For notes: `EE202_Lecture#_Topic.pdf`
+- For assignments: `EE202_Assignment#_YYYY.pdf`🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@branch/electrical/SEM3/EE202/index.md` around lines 49 - 64, Update the
contributing example block and naming conventions to reference the correct
course code and fence language: replace all occurrences of "CE102" with "EE202"
inside the code fence and in the three naming-convention examples (exams, notes,
assignments), and change the fenced block language from ``` to ```text so the
snippet shows as plain text; target the code sample under the "Option B: Add
Drive Links (Recommended)" section and the three bullet lines beginning with
"For exams:", "For notes:", and "For assignments:" to make the page
course-accurate.
Comment on lines
+53
to
+68
| ``` | ||
| CE102/ | ||
| ├── CE102_Mid_2024.pdf | ||
| ├── CE102_End_2023.pdf | ||
| └── CE102_Notes_TopicX.pdf | ||
| ``` | ||
|
|
||
| ### Option B: Add Drive Links (Recommended) | ||
|
|
||
| Add your Google Drive share link to the table above following the existing format. | ||
|
|
||
| **📝 Naming Convention** | ||
|
|
||
| - For exams: `CE102_Mid_YYYY.pdf` or `CE102_End_YYYY.pdf` | ||
| - For notes: `CE102_Lecture#_Topic.pdf` | ||
| - For assignments: `CE102_Assignment#_YYYY.pdf` |
There was a problem hiding this comment.
Align the contributing snippet with EE203.
The code fence should be typed as text, and the CE102 examples should be replaced with EE203 or <COURSE_CODE> so contributors do not follow the wrong folder/prefix pattern.
Suggested fix
-```
-CE102/
-├── CE102_Mid_2024.pdf
-├── CE102_End_2023.pdf
-└── CE102_Notes_TopicX.pdf
-```
+```text
+EE203/
+├── EE203_Mid_2024.pdf
+├── EE203_End_2023.pdf
+└── EE203_Notes_TopicX.pdf
+```
-- For exams: `CE102_Mid_YYYY.pdf` or `CE102_End_YYYY.pdf`
-- For notes: `CE102_Lecture#_Topic.pdf`
-- For assignments: `CE102_Assignment#_YYYY.pdf`
+- For exams: `EE203_Mid_YYYY.pdf` or `EE203_End_YYYY.pdf`
+- For notes: `EE203_Lecture#_Topic.pdf`
+- For assignments: `EE203_Assignment#_YYYY.pdf`📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ``` | |
| CE102/ | |
| ├── CE102_Mid_2024.pdf | |
| ├── CE102_End_2023.pdf | |
| └── CE102_Notes_TopicX.pdf | |
| ``` | |
| ### Option B: Add Drive Links (Recommended) | |
| Add your Google Drive share link to the table above following the existing format. | |
| **📝 Naming Convention** | |
| - For exams: `CE102_Mid_YYYY.pdf` or `CE102_End_YYYY.pdf` | |
| - For notes: `CE102_Lecture#_Topic.pdf` | |
| - For assignments: `CE102_Assignment#_YYYY.pdf` |
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 53-53: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@branch/electrical/SEM3/EE203/index.md` around lines 53 - 68, The snippet
shows CE102 examples and an untyped code fence; update the fenced example in
index.md to use a language tag of "text" (change ``` to ```text) and replace all
CE102-specific folder and filename examples and naming convention lines with
EE203 (or a generic <COURSE_CODE>) so contributors follow the EE203
pattern—specifically modify the block that lists the folder (CE102/ and CE102_*
filenames) and the three naming convention bullets (exams, notes, assignments)
to use EE203_* equivalents and ensure the fence is closed with ``` as ```text.
Comment on lines
+48
to
+63
| ``` | ||
| CE102/ | ||
| ├── CE102_Mid_2024.pdf | ||
| ├── CE102_End_2023.pdf | ||
| └── CE102_Notes_TopicX.pdf | ||
| ``` | ||
|
|
||
| ### Option B: Add Drive Links (Recommended) | ||
|
|
||
| Add your Google Drive share link to the table above following the existing format. | ||
|
|
||
| **📝 Naming Convention** | ||
|
|
||
| - For exams: `CE102_Mid_YYYY.pdf` or `CE102_End_YYYY.pdf` | ||
| - For notes: `CE102_Lecture#_Topic.pdf` | ||
| - For assignments: `CE102_Assignment#_YYYY.pdf` |
There was a problem hiding this comment.
Fix the course code in the contributing guide.
CE102 looks copy-pasted from another page, so contributors here may follow the wrong naming pattern. Also add text to the fenced block.
Suggested fix
-```
-CE102/
-├── CE102_Mid_2024.pdf
-├── CE102_End_2023.pdf
-└── CE102_Notes_TopicX.pdf
-```
+```text
+EE204/
+├── EE204_Mid_2024.pdf
+├── EE204_End_2023.pdf
+└── EE204_Notes_TopicX.pdf
+```
-- For exams: `CE102_Mid_YYYY.pdf` or `CE102_End_YYYY.pdf`
-- For notes: `CE102_Lecture#_Topic.pdf`
-- For assignments: `CE102_Assignment#_YYYY.pdf`
+- For exams: `EE204_Mid_YYYY.pdf` or `EE204_End_YYYY.pdf`
+- For notes: `EE204_Lecture#_Topic.pdf`
+- For assignments: `EE204_Assignment#_YYYY.pdf`🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 48-48: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@branch/electrical/SEM3/EE204/index.md` around lines 48 - 63, The contributing
guide erroneously uses the CE102 course code and a plain fenced block; update
the sample tree and naming examples to use the correct course code "EE204"
everywhere (change instances of "CE102" in the fenced block and the three naming
convention lines to "EE204") and mark the fenced block as text by adding the
language tag (replace the opening ``` with ```text) so the snippet and naming
convention align with EE204.
Comment on lines
+48
to
+63
| ``` | ||
| CE102/ | ||
| ├── CE102_Mid_2024.pdf | ||
| ├── CE102_End_2023.pdf | ||
| └── CE102_Notes_TopicX.pdf | ||
| ``` | ||
|
|
||
| ### Option B: Add Drive Links (Recommended) | ||
|
|
||
| Add your Google Drive share link to the table above following the existing format. | ||
|
|
||
| **📝 Naming Convention** | ||
|
|
||
| - For exams: `CE102_Mid_YYYY.pdf` or `CE102_End_YYYY.pdf` | ||
| - For notes: `CE102_Lecture#_Topic.pdf` | ||
| - For assignments: `CE102_Assignment#_YYYY.pdf` |
There was a problem hiding this comment.
Make the contributing example match this page.
The fenced block should declare a language (for lint/readability), and the CE102 examples are misleading on an EE205 page. Use EE205 here or a generic placeholder like <COURSE_CODE>.
Suggested fix
-```
-CE102/
-├── CE102_Mid_2024.pdf
-├── CE102_End_2023.pdf
-└── CE102_Notes_TopicX.pdf
-```
+```text
+EE205/
+├── EE205_Mid_2024.pdf
+├── EE205_End_2023.pdf
+└── EE205_Notes_TopicX.pdf
+```
-- For exams: `CE102_Mid_YYYY.pdf` or `CE102_End_YYYY.pdf`
-- For notes: `CE102_Lecture#_Topic.pdf`
-- For assignments: `CE102_Assignment#_YYYY.pdf`
+- For exams: `EE205_Mid_YYYY.pdf` or `EE205_End_YYYY.pdf`
+- For notes: `EE205_Lecture#_Topic.pdf`
+- For assignments: `EE205_Assignment#_YYYY.pdf`🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 48-48: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@branch/electrical/SEM3/EE205/index.md` around lines 48 - 63, Update the
README example block and naming conventions to match EE205: change the fenced
code block to declare a language (e.g., ```text) and replace all CE102 examples
with EE205 (or a <COURSE_CODE> placeholder) so the tree and subsequent naming
bullets use EE205 consistently; edit the fenced block and the three bullets
referencing exams/notes/assignments near the "Option B: Add Drive Links
(Recommended)" section to reflect this.
Comment on lines
+26
to
+36
| <a href="#📚-subjects"><b>Explore →</b></a> | ||
| </td> | ||
| <td align="center" width="33%"> | ||
| <img src="https://img.shields.io/badge/🧪-LABS-10B981?style=flat-square&labelColor=065F46" alt="Labs"/><br/> | ||
| <sub>Practical sessions</sub><br/> | ||
| <a href="#🧪-labs"><b>Explore →</b></a> | ||
| </td> | ||
| <td align="center" width="33%"> | ||
| <img src="https://img.shields.io/badge/📖-PYQS-F59E0B?style=flat-square&labelColor=92400E" alt="PYQs"/><br/> | ||
| <sub>Previous year papers</sub><br/> | ||
| <a href="#📖-pyqs"><b>Explore →</b></a> |
There was a problem hiding this comment.
Fix the section anchors.
These fragments are unlikely to match the generated heading IDs, so the quick-nav links and the PYQ shortcut can fail to jump to the target section.
Suggested fix
-## 📚 Subjects
+<h2 id="subjects">📚 Subjects</h2>
-## 🧪 Labs
+<h2 id="labs">🧪 Labs</h2>
-## 📖 PYQs
+<h2 id="pyqs">📖 PYQs</h2>
-<a href="#📚-subjects"><b>Explore →</b></a>
+<a href="#subjects"><b>Explore →</b></a>
-<a href="#🧪-labs"><b>Explore →</b></a>
+<a href="#labs"><b>Explore →</b></a>
-<a href="#📖-pyqs"><b>Explore →</b></a>
+<a href="#pyqs"><b>Explore →</b></a>
-Navigate to any subject using the [📚 Subjects section ↑](#📚-subjects) to access its dedicated PYQ collection.
+Navigate to any subject using the [📚 Subjects section ↑](`#subjects`) to access its dedicated PYQ collection.Also applies to: 119-119
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@branch/electrical/SEM3/index.md` around lines 26 - 36, The quick-nav links
use fragments like "#📚-subjects", "#🧪-labs" and "#📖-pyqs" which likely don't
match the markdown-generated heading IDs; update the anchors so they match the
actual slugified heading IDs or add explicit HTML id attributes on the target
headings (e.g., give the "📚 Subjects", "🧪 Labs" and "📖 PYQs" headings
explicit ids and then change the hrefs to those ids), and apply the same
correction for the similar anchor at the other occurrence (the one referenced at
line 119).
Comment on lines
+26
to
+36
| <a href="#📚-subjects"><b>Explore →</b></a> | ||
| </td> | ||
| <td align="center" width="33%"> | ||
| <img src="https://img.shields.io/badge/🧪-LABS-10B981?style=flat-square&labelColor=065F46" alt="Labs"/><br/> | ||
| <sub>Practical sessions</sub><br/> | ||
| <a href="#🧪-labs"><b>Explore →</b></a> | ||
| </td> | ||
| <td align="center" width="33%"> | ||
| <img src="https://img.shields.io/badge/📖-PYQS-F59E0B?style=flat-square&labelColor=92400E" alt="PYQs"/><br/> | ||
| <sub>Previous year papers</sub><br/> | ||
| <a href="#📖-pyqs"><b>Explore →</b></a> |
There was a problem hiding this comment.
Use stable section ids for in-page navigation.
These emoji fragments are likely not resolving to the actual heading IDs, so the quick-nav cards and the PYQ shortcut can break.
Suggested fix
-## 📚 Subjects
+<h2 id="subjects">📚 Subjects</h2>
-## 🧪 Labs
+<h2 id="labs">🧪 Labs</h2>
-## 📖 PYQs
+<h2 id="pyqs">📖 PYQs</h2>
-<a href="#📚-subjects"><b>Explore →</b></a>
+<a href="#subjects"><b>Explore →</b></a>
-<a href="#🧪-labs"><b>Explore →</b></a>
+<a href="#labs"><b>Explore →</b></a>
-<a href="#📖-pyqs"><b>Explore →</b></a>
+<a href="#pyqs"><b>Explore →</b></a>
-Navigate to any subject using the [📚 Subjects section ↑](#📚-subjects) to access its dedicated PYQ collection.
+Navigate to any subject using the [📚 Subjects section ↑](`#subjects`) to access its dedicated PYQ collection.Also applies to: 120-120
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@branch/electrical/SEM4/index.md` around lines 26 - 36, The in-page quick-nav
links use emoji-based fragment IDs ("#📚-subjects", "#🧪-labs", "#📖-pyqs")
which are unstable; change these hrefs to match the actual heading IDs (e.g.,
"#subjects", "#labs", "#pyqs") or add explicit id attributes on the
corresponding headings so they resolve reliably, and update the anchor targets
in the index.md card block that contains the three links to use those stable
ids.
|
|
||
| ## 📚 Subjects | ||
|
|
||
| _Core SEM 3 curriculum — Click to explore_ |
There was a problem hiding this comment.
Correct the semester label here.
This is the SEM4 hub, but the subtitle still says "SEM 3", which makes the page look copied without being fully updated.
Suggested fix
-_Core SEM 3 curriculum — Click to explore_
+_Core SEM 4 curriculum — Click to explore_📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| _Core SEM 3 curriculum — Click to explore_ | |
| _Core SEM 4 curriculum — Click to explore_ |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@branch/electrical/SEM4/index.md` at line 48, The subtitle text currently
reads "_Core SEM 3 curriculum — Click to explore_" and should be updated to
reflect this is the SEM4 hub; locate that string in index.md and change "SEM 3"
to "SEM 4" so it reads "_Core SEM 4 curriculum — Click to explore_"; verify
there are no other occurrences of "SEM 3" on the page and update any remaining
mismatched semester labels to "SEM 4".
RAJ8664
approved these changes
Mar 9, 2026
Owner
Consider adding meaningful name to the pdfs from next time. |
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
👋 Hey there! Thank you for contributing to Prep 🚀
Please fill out this pull request template carefully to help us review your changes quickly.
Please check all that apply:
Place an "x" in the corresponding checkboxSummary by CodeRabbit