Skip to content

Commit 0fb1fd6

Browse files
committed
Merge remote-tracking branch 'refs/remotes/origin/main'
2 parents 0c34dd2 + 61a3c4b commit 0fb1fd6

1 file changed

Lines changed: 41 additions & 92 deletions

File tree

src/components/Onboarding/CreateForkStatic.jsx

Lines changed: 41 additions & 92 deletions
Original file line numberDiff line numberDiff line change
@@ -19,20 +19,21 @@ const steps = [
1919
subtitle: "Create your personal copy on GitHub",
2020
commands: [
2121
{
22-
command: "# 1. Go to the repository on GitHub",
23-
description: "Navigate to the project's GitHub page",
22+
command:
23+
"# 1. Open the repo: https://github.com/devclub-nstru/DCODE-Smaple-Repo",
24+
description: "Go to the GitHub repository",
2425
},
2526
{
2627
command: "# 2. Click the 'Fork' button (top-right)",
27-
description: "This creates a copy under your account",
28+
description: "This creates a copy under your GitHub account",
2829
},
2930
{
3031
command: "# 3. Choose your account as destination",
31-
description: "Select where to create the fork",
32+
description: "Select your GitHub account",
3233
},
3334
{
3435
command: "# 4. Wait for GitHub to create the fork",
35-
description: "GitHub will redirect you to your fork",
36+
description: "GitHub will redirect you to your forked repo",
3637
},
3738
],
3839
},
@@ -42,7 +43,7 @@ const steps = [
4243
title: "Clone your",
4344
highlight: "fork",
4445
blurb: "Bring your fork down to your machine.",
45-
body: "Cloning downloads your forked repository to your local computer so you can make changes. Use git to clone your fork and set up the connection to the original repository for future updates.",
46+
body: "Cloning downloads your forked repository to your local computer so you can make changes. Use git to clone your fork and move into the directory.",
4647
icon: "📥",
4748
color: "#BCDD19",
4849
snippet: {
@@ -51,110 +52,64 @@ const steps = [
5152
commands: [
5253
{
5354
command:
54-
"git clone https://github.com/<your-username>/<repository-name>.git",
55-
description: "Clone your forked repository",
55+
"git clone https://github.com/<your-username>/DCODE-Smaple-Repo.git",
56+
description: "Clone your forked repository (replace <your-username>)",
5657
},
5758
{
58-
command: "cd <repository-name>",
59+
command: "cd DCODE-Smaple-Repo",
5960
description: "Navigate into the project directory",
6061
},
6162
{
62-
command:
63-
"git remote add upstream https://github.com/<original-owner>/<repository-name>.git",
64-
description: "Add the original repository as upstream remote",
65-
},
66-
{
67-
command: "git remote -v",
68-
description: "Verify your remote repositories are set up correctly",
63+
command: "# Open VS Code",
64+
description: "Open the project in VS Code",
6965
},
7066
],
7167
},
7268
},
7369
{
7470
id: 3,
75-
title: "Create a",
76-
highlight: "branch",
77-
blurb: "Keep your changes isolated and easy to review.",
78-
body: "Creating a new branch keeps your changes separate from the main code. This makes it easier to manage multiple contributions and allows maintainers to review your changes without conflicts.",
79-
icon: "🌿",
80-
color: "#BCDD19",
81-
snippet: {
82-
label: "Create Branch",
83-
subtitle: "Create a new branch for your feature or bug fix",
84-
commands: [
85-
{
86-
command: "git checkout -b feature/<descriptive-name>",
87-
description: "Create and switch to a new feature branch",
88-
},
89-
{
90-
command: "# Example: git checkout -b fix/button-alignment",
91-
description: "Use descriptive names for your branches",
92-
},
93-
{
94-
command: "git status",
95-
description: "Confirm you're on the new branch",
96-
},
97-
{
98-
command: "# Now make your changes to the code",
99-
description: "Edit files using your preferred code editor",
100-
},
101-
],
102-
},
103-
},
104-
{
105-
id: 4,
10671
title: "Make your",
10772
highlight: "changes",
108-
blurb: "Implement your feature or fix the issue.",
109-
body: "Now comes the actual coding! Make your changes carefully, following the project's coding standards and guidelines. Test your changes thoroughly to ensure they work as expected and don't break existing functionality.",
73+
blurb: "Add your name to the README file.",
74+
body: "Now, edit the README file in VS Code and add your name under the contributors section. This is the task for contributing to this repository.",
11075
icon: "✏️",
11176
color: "#BCDD19",
11277
snippet: {
113-
label: "Making Changes",
114-
subtitle: "Best practices for implementing your contribution",
78+
label: "Update README",
79+
subtitle: "Add your name to the README file",
11580
commands: [
11681
{
117-
command: "# 1. Read the CONTRIBUTING.md file",
118-
description: "Understand the project's contribution guidelines",
119-
},
120-
{
121-
command: "# 2. Install dependencies",
122-
description: "Run npm install, pip install, etc.",
82+
command: "# In VS Code, open README.md",
83+
description: "Use the Explorer panel to open README.md",
12384
},
12485
{
125-
command: "# 3. Make your changes",
126-
description: "Edit the necessary files",
127-
},
128-
{
129-
command: "# 4. Test your changes locally",
130-
description: "Run tests and verify functionality",
86+
command: "# Add your name under the contributors section",
87+
description: "Save the file after editing",
13188
},
13289
],
13390
},
13491
},
13592
{
136-
id: 5,
93+
id: 4,
13794
title: "Commit your",
13895
highlight: "changes",
13996
blurb: "Save your work with a clear message.",
140-
body: "Commits create snapshots of your changes. Write clear, descriptive commit messages that explain what you changed and why. Follow conventional commit format if the project uses it.",
97+
body: "Commits create snapshots of your changes. Write a clear, descriptive commit message explaining what you did.",
14198
icon: "💾",
14299
color: "#BCDD19",
143100
snippet: {
144101
label: "Commit Changes",
145102
subtitle: "Save your work with descriptive commit messages",
146103
commands: [
147104
{
148-
command: "git add .",
149-
description: "Stage all your changes",
105+
command: "git add README.md",
106+
description: "Stage the README file changes",
150107
},
151108
{
152-
command: "git commit -m 'feat: add user authentication feature'",
153-
description: "Commit with a clear, descriptive message",
154-
},
155-
{
156-
command: "# Alternative: git add <specific-files>",
157-
description: "Stage only specific files if preferred",
109+
command:
110+
"git commit -m 'chore: add <your-name> to contributors list'",
111+
description:
112+
"Commit with a clear, descriptive message (replace <your-name>)",
158113
},
159114
{
160115
command: "git log --oneline",
@@ -164,28 +119,20 @@ const steps = [
164119
},
165120
},
166121
{
167-
id: 6,
122+
id: 5,
168123
title: "Push to",
169124
highlight: "GitHub",
170125
blurb: "Upload your changes to your fork.",
171-
body: "Pushing uploads your local commits to your GitHub fork. This makes your changes visible on GitHub and prepares them for creating a pull request to the original repository.",
172-
icon: "",
126+
body: "Pushing uploads your local commits to your GitHub fork. This makes your changes visible on GitHub.",
127+
icon: "🚀",
173128
color: "#BCDD19",
174129
snippet: {
175130
label: "Push Changes",
176131
subtitle: "Upload your commits to your GitHub fork",
177132
commands: [
178133
{
179-
command: "git push origin <your-branch-name>",
180-
description: "Push your branch to your GitHub fork",
181-
},
182-
{
183-
command: "# Example: git push origin feature/user-auth",
184-
description: "Push your specific feature branch",
185-
},
186-
{
187-
command: "# For first push: git push -u origin <branch-name>",
188-
description: "Set upstream tracking for future pushes",
134+
command: "git push origin main",
135+
description: "Push your commit to your fork’s main branch",
189136
},
190137
{
191138
command: "git status",
@@ -195,28 +142,29 @@ const steps = [
195142
},
196143
},
197144
{
198-
id: 7,
145+
id: 6,
199146
title: "Create a",
200147
highlight: "Pull Request",
201148
blurb: "Propose your changes to the original project.",
202-
body: "A Pull Request (PR) is how you propose your changes to be merged into the original project. Write a clear description of what you changed, why you changed it, and any relevant information for reviewers.",
203-
icon: "",
149+
body: "A Pull Request (PR) is how you propose your changes to be merged into the original project. Write a clear description of what you changed and why.",
150+
icon: "🔀",
204151
color: "#BCDD19",
205152
snippet: {
206153
label: "Create Pull Request",
207154
subtitle: "Submit your contribution for review",
208155
commands: [
209156
{
210157
command: "# 1. Go to your fork on GitHub",
211-
description: "Navigate to your repository on GitHub",
158+
description: "Navigate to your forked repository",
212159
},
213160
{
214161
command: "# 2. Click 'Compare & pull request'",
215162
description: "GitHub will show this button after pushing",
216163
},
217164
{
218165
command: "# 3. Write a clear title and description",
219-
description: "Explain what your changes do and why",
166+
description:
167+
"E.g., 'Added Aditya Kumar to contributors list in README'",
220168
},
221169
{
222170
command: "# 4. Click 'Create pull request'",
@@ -298,7 +246,8 @@ export default function CreateFork() {
298246
<>
299247
<div className="mb-[1.5rem] bg-transparent">
300248
<h1 className="text-4xl font-bold text-center">
301-
Let's start with your first <span className="text-[#BCDD19]">PR</span>{" "}
249+
Let's start with your first{" "}
250+
<span className="text-[#BCDD19]">PR</span>{" "}
302251
</h1>
303252
<p className="text-lg text-[#A1A1AA] mt-2 text-center">
304253
Let's get you started on your contribution journey

0 commit comments

Comments
 (0)