Skip to content

Conversation

@Mishu03
Copy link

@Mishu03 Mishu03 commented Oct 25, 2025

What has been added/changed?

  • Added a "Troubleshooting & Common Issues" section to help beginners address frequent Git and GitHub problems, including command errors, authentication, merge conflicts, and dependency installation.
  • Included a "Real-World Use Cases & Examples" section showcasing how GitHub supports teamwork, issue tracking, and open-source contributions.
  • Linked to helpful resources and guides for deeper troubleshooting.

Why?

These improvements make the documentation more accessible to new contributors by providing practical, actionable guidance and real-world scenarios. It helps users resolve common roadblocks and understand collaborative workflows.

Testing Steps

  • Review rendered Markdown for formatting and clarity in VS Code preview
  • Confirm all code blocks and external links function as expected

@vercel
Copy link
Contributor

vercel bot commented Oct 25, 2025

@Mishu03 is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions
Copy link

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

  1. Get free Consultation use code recode50 to get free: Mentorship for free.

  2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

  3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

@github-actions github-actions bot added hacktoberfest-accepted recode this is label for leaderboard labels Oct 25, 2025
@@ -0,0 +1,17 @@
// src/components/ConfettiUtils.tsx
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The file path comment is incorrect - the file is in src/utils/ not src/components/, which suggests confusion about the actual file location.

View Details
📝 Patch Details
diff --git a/src/components/tutorialCompletion.tsx b/src/components/tutorialCompletion.tsx
index 8d5f57c..3c146ae 100644
--- a/src/components/tutorialCompletion.tsx
+++ b/src/components/tutorialCompletion.tsx
@@ -1,6 +1,6 @@
 // src/components/tutorialCompletion.tsx
 import React, { useState } from 'react';
-import { triggerConfetti } from './ConfettiUtils';  // Import from the separate confetti utility
+import { triggerConfetti } from '../utils/ConfettiUtils';  // Import from the separate confetti utility
 
 interface TutorialCompletionProps {
   tutorialTitle?: string;  // Optional prop for the tutorial name
diff --git a/src/utils/ConfettiUtils.tsx b/src/utils/ConfettiUtils.tsx
index 5088a36..a32a92e 100644
--- a/src/utils/ConfettiUtils.tsx
+++ b/src/utils/ConfettiUtils.tsx
@@ -1,4 +1,4 @@
-// src/components/ConfettiUtils.tsx
+// src/utils/ConfettiUtils.tsx
 import confetti from 'canvas-confetti';
 
 /**

Analysis

Incorrect file path comment in ConfettiUtils.tsx

What fails: File comment in src/utils/ConfettiUtils.tsx incorrectly states // src/components/ConfettiUtils.tsx, causing confusion about file location and contributing to incorrect import path in tutorialCompletion.tsx

How to reproduce: Check line 1 of src/utils/ConfettiUtils.tsx - comment shows wrong directory

Result: Comment shows // src/components/ConfettiUtils.tsx but file is actually in src/utils/ directory

Expected: Comment should accurately reflect actual file path as // src/utils/ConfettiUtils.tsx (consistent with other files in codebase that have correct path comments)

Additional context: This incorrect comment contributed to the wrong import path './ConfettiUtils' in tutorialCompletion.tsx which was importing from non-existent relative path

@@ -0,0 +1,62 @@
// src/components/tutorialCompletion.tsx
import React, { useState } from 'react';
import { triggerConfetti } from './ConfettiUtils'; // Import from the separate confetti utility
Copy link
Contributor

@vercel vercel bot Oct 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
import { triggerConfetti } from './ConfettiUtils'; // Import from the separate confetti utility
import { triggerConfetti } from '../utils/ConfettiUtils'; // Import from the separate confetti utility

The import path for ConfettiUtils is incorrect - it's in the utils directory, not the components directory, which will cause a module resolution error at runtime.

View Details

Analysis

Incorrect import path causes module resolution error in TutorialCompletion component

What fails: TutorialCompletion component imports triggerConfetti from './ConfettiUtils' but ConfettiUtils.tsx is located in src/utils/, not src/components/

How to reproduce:

npm run build

Result: Build fails with error: Module not found: Error: Can't resolve './ConfettiUtils' in '/vercel/sandbox/sandpits/kind-crow/src/components'

Expected: Import should resolve correctly to src/utils/ConfettiUtils.tsx using relative path '../utils/ConfettiUtils'

git config --global user.name "Your Name"
git config --global user.email "[email protected]"
- Use a Personal Access Token instead of a password for GitHub authentication. Learn how to [set up a token here](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
- Confirm you’re pushing to the right repo:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Confirm you’re pushing to the right repo:
- Confirm you’re pushing to the right repo: Check your remote URL with `git remote -v` and ensure it matches the correct repository.

Incomplete bullet point: "Confirm you're pushing to the right repo:" has no guidance following it, leaving the troubleshooting solution unfinished.

View Details

Analysis

Incomplete troubleshooting bullet point in GitHub documentation

What fails: Line 114 in docs/GitHub/intro-github.md contains incomplete guidance: "Confirm you're pushing to the right repo:" with no actionable instructions

How to reproduce:

  1. Open docs/GitHub/intro-github.md
  2. Navigate to line 114 in the "Cannot Push to Repository" troubleshooting section
  3. Observe the bullet point ends with a colon but provides no command or guidance

Result: Users are left without actionable steps to verify their repository configuration

Expected: Bullet points in troubleshooting sections should provide complete, actionable guidance per the established pattern in the same document

Fix: Added the standard GitHub-recommended command: "Check your remote URL with git remote -v and ensure it matches the correct repository" as documented in GitHub's official remote management guide

To make this more practical, let's create a simple "Hello World" project:
1. In your terminal, create a new directory:
mkdir my-first-node-project cd my-first-node-project
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
mkdir my-first-node-project cd my-first-node-project
mkdir my-first-node-project && cd my-first-node-project

Two shell commands are incorrectly combined on a single line without proper separation. A beginner following this tutorial will get an error when trying to execute this command.

View Details

Analysis

Shell commands incorrectly combined without separator in Node.js setup tutorial

What fails: Line 74 in docs/NodeJS-Setup/index.md contains mkdir my-first-node-project cd my-first-node-project which combines two shell commands without proper separation

How to reproduce:

mkdir my-first-node-project cd my-first-node-project

Result: Creates directories named "my-first-node-project" and "cd" instead of creating directory and changing into it. Shell interprets cd as an argument to mkdir

Expected: Should create directory and then change into it. Fixed by adding && operator: mkdir my-first-node-project && cd my-first-node-project

@sanjay-kv
Copy link
Member

so many other pages changed irrelavant what the original issue.

@sanjay-kv sanjay-kv closed this Oct 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hacktoberfest-accepted recode this is label for leaderboard

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants