Feature update - #28
Conversation
📝 WalkthroughWalkthroughThe PR adds several new documentation and placeholder files while deleting the existing Day 01 README. It introduces a personal learning plan document, git commands solution guide, and dummy placeholder files for week 04 challenges. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@2025/week-04-challenge/challenge1/info.txt`:
- Around line 1-4: Remove the placeholder lines ("this is dummy data", "this
will be from feature-update") in info.txt and either delete the file if it's
unnecessary or replace its contents with meaningful challenge metadata: a short
challenge title, learning objectives, problem description, input/output format,
constraints, and any examples or setup notes so the challenge directory is not
polluted with dummy content.
In `@2025/week-04-challenge/info.txt`:
- Line 1: Remove the placeholder dummy content from the file named info.txt in
this challenge (it currently contains "this is dummy data"); either delete the
file entirely if it provides no value or replace its contents with the intended
challenge description or real metadata so the repository contains only
purposeful files before merging.
In `@2026/day-01/learning-plan.md`:
- Around line 1-44: The repo changed 2026/day-01/learning-plan.md but removed
2026/day-01/README.md, which prevents GitHub from auto-rendering the directory;
either rename learning-plan.md to README.md (replace the deleted README) or add
a new README.md in the same directory that contains a short title and a
link/summary pointing to learning-plan.md so the learning plan is rendered when
browsing 2026/day-01; update any references or links in the PR if you rename the
file to README.md.
- Line 14: Replace the flagged spelling/capitalization errors in
learning-plan.md: change "shooked" to "shaken" in the sentence containing "can't
be shaken by anyone" (line with that phrase), change "Buddget" to "Budget"
wherever "Buddget" appears, and change "Youtube" to the proper capitalization
"YouTube" wherever "Youtube" appears; ensure you only modify the misspelled
words and preserve existing punctuation and casing elsewhere.
In `@info.txt`:
- Line 1: Delete the repository root placeholder file named info.txt (which
contains "this is dummy file") from the PR so the top-level directory is not
polluted; remove the file from the commit/branch and ensure no other references
to info.txt remain in the repo or CI configuration before merging.
| this is dummy data | ||
|
|
||
| this will be from feature-update | ||
|
|
There was a problem hiding this comment.
Remove placeholder/dummy content before merging.
The content of this file ("this is dummy data", "this will be from feature-update") is a Git workflow practice artifact and has no value in a shared community repository. Committing it to master would pollute the challenge directory with noise.
Please either replace this with meaningful challenge-related content or remove the file entirely.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@2025/week-04-challenge/challenge1/info.txt` around lines 1 - 4, Remove the
placeholder lines ("this is dummy data", "this will be from feature-update") in
info.txt and either delete the file if it's unnecessary or replace its contents
with meaningful challenge metadata: a short challenge title, learning
objectives, problem description, input/output format, constraints, and any
examples or setup notes so the challenge directory is not polluted with dummy
content.
| # Day 01 -Introduction to Devops And Cloud | ||
|
|
||
| ## My Introduction to My DevOps Journey | ||
| Hi My Name Is Shubham Chavan, | ||
|
|
||
| What Defines my Learning plan is: | ||
|
|
||
| My Understanding about DevOps & Cloud Engineering: | ||
|
|
||
| -For Me Personally As a biased IT Guy, System Administration was a One Thing At My Bachelor Years where i use to work as lab-assistant ,but when i was introduced to firewalls and server related stuff i got to know about how the whole system works around & how a system-administrator has a lot of responsibilities of the whole college. Later On , I Started My Learning Through AWS Cloud On Youtube & then Recognizing what DevOps &Cloud Engineering Fulfills the responsibilities that No One Can Do IS My Thing That I LOVE A Lot To DO. | ||
|
|
||
| -My Ultimate Goal Is To Become DevOps Engineer With (The Highest Package The Industry Has To Offer) | ||
|
|
||
| -I Know My Limits Better than anyone out there, So i Have faith,courage,wisdom,confidence in myself that can't be shooked by anyone whether its my family,friends or any other out there. | ||
|
|
||
| --- | ||
|
|
||
| ## My Current Level | ||
| -My Current Level is Student(Part-Time Employee In Ed-Tech Institute). | ||
|
|
||
| ## My Current Goals for 2026 (Next 3 Months i.e From FEB) | ||
| My 3 Clear Goals for the next 90 Days | ||
|
|
||
| - To Remove the fact that this challenge can't be done by anyone with JOSH. | ||
|
|
||
| - To Learn About DevOps Engineering and the backend process of how it powers the upcoming Technologies. | ||
|
|
||
| - There is No Plan B. | ||
|
|
||
| ## My 3 Core DevOps Skills Which I Want To Build | ||
| My 3 Core DevOps Skills which i want to build is | ||
|
|
||
| - Troubleshooting & Debugging. | ||
|
|
||
| - Learn Concepts like terraform, kubernetes and much more | ||
|
|
||
| - Expressing your Work To Others (Which I Lack A Lot.) | ||
|
|
||
| ## My Weekly Time Budget | ||
| My Weekly Time Buddget is | ||
|
|
||
| - On Weekdays i.e (Mon To Fri) will be ~3.5hrs (7 pm to 10 pm) | ||
|
|
||
| - On WeekEnds i.e (Sat To Sun) will be ~5hrs (6pm to 11 pm) |
There was a problem hiding this comment.
Consider renaming to README.md (or adding one) so GitHub renders the directory.
The AI summary notes that 2026/day-01/README.md was deleted in this PR and replaced by this learning-plan.md. GitHub only auto-renders a file named README.md when browsing a directory, so visitors to 2026/day-01/ will now see a raw file listing instead of the formatted learning plan. Renaming this file to README.md, or adding a minimal README.md that links to learning-plan.md, would restore discoverability.
🧰 Tools
🪛 LanguageTool
[style] ~10-~10: It might be better to use ‘Years’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...stration was a One Thing At My Bachelor Years where i use to work as lab-assistant ,but whe...
(WHEN_WHERE)
[grammar] ~10-~10: Use a hyphen to join words.
Context: ...i was introduced to firewalls and server related stuff i got to know about how t...
(QB_NEW_EN_HYPHEN)
[style] ~10-~10: Consider using a synonym to be more concise.
Context: ...around & how a system-administrator has a lot of responsibilities of the whole college. ...
(A_LOT_OF)
[uncategorized] ~10-~10: The official name of this popular video platform is spelled with a capital “T”.
Context: ...tarted My Learning Through AWS Cloud On Youtube & then Recognizing what DevOps &Cloud E...
(YOUTUBE)
[grammar] ~14-~14: Ensure spelling is correct
Context: ...sdom,confidence in myself that can't be shooked by anyone whether its my family,friends...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@2026/day-01/learning-plan.md` around lines 1 - 44, The repo changed
2026/day-01/learning-plan.md but removed 2026/day-01/README.md, which prevents
GitHub from auto-rendering the directory; either rename learning-plan.md to
README.md (replace the deleted README) or add a new README.md in the same
directory that contains a short title and a link/summary pointing to
learning-plan.md so the learning plan is rendered when browsing 2026/day-01;
update any references or links in the PR if you rename the file to README.md.
|
|
||
| -My Ultimate Goal Is To Become DevOps Engineer With (The Highest Package The Industry Has To Offer) | ||
|
|
||
| -I Know My Limits Better than anyone out there, So i Have faith,courage,wisdom,confidence in myself that can't be shooked by anyone whether its my family,friends or any other out there. |
There was a problem hiding this comment.
Fix a few spelling errors flagged by static analysis.
- Line 14:
shooked→shaken("can't be shaken by anyone") - Line 40:
Buddget→Budget - Line 10:
Youtube→YouTube(official capitalization)
✏️ Proposed fixes
-in myself that can't be shooked by anyone whether its my family,friends or any other out there.
+in myself that can't be shaken by anyone whether its my family,friends or any other out there.-My Weekly Time Buddget is
+My Weekly Time Budget is-Started My Learning Through AWS Cloud On Youtube & then
+Started My Learning Through AWS Cloud On YouTube & thenAlso applies to: 40-40
🧰 Tools
🪛 LanguageTool
[grammar] ~14-~14: Ensure spelling is correct
Context: ...sdom,confidence in myself that can't be shooked by anyone whether its my family,friends...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@2026/day-01/learning-plan.md` at line 14, Replace the flagged
spelling/capitalization errors in learning-plan.md: change "shooked" to "shaken"
in the sentence containing "can't be shaken by anyone" (line with that phrase),
change "Buddget" to "Budget" wherever "Buddget" appears, and change "Youtube" to
the proper capitalization "YouTube" wherever "Youtube" appears; ensure you only
modify the misspelled words and preserve existing punctuation and casing
elsewhere.
| @@ -0,0 +1 @@ | |||
| this is dummy file | |||
There was a problem hiding this comment.
Remove this dummy file from the repository root.
A placeholder file at the repo root with content "this is dummy file" serves no purpose and pollutes the top-level directory of a community repository. This should be removed before the PR is merged.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@info.txt` at line 1, Delete the repository root placeholder file named
info.txt (which contains "this is dummy file") from the PR so the top-level
directory is not polluted; remove the file from the commit/branch and ensure no
other references to info.txt remain in the repo or CI configuration before
merging.
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@2025/week-04-challenge/solution.md`:
- Line 1: Update the heading text to use proper grammar and formatting: replace
the phrase "task1-4" with "tasks 1–4" (use an en dash) and remove the
non-standard ":-" suffix—either end the line with a simple ":" or place a blank
line after the heading before the list; ensure the revised line reads something
like "The Commands used in tasks 1–4:" or the heading followed by a blank line
and the list.
- Around line 7-8: The listed git steps are out of order: "git push origin
<branch name>" appears before "git remote add origin ..."; update the sequence
so git remote add origin "url of git repo" comes before git push origin <branch
name> (i.e., swap the two steps) to ensure the remote exists before pushing.
| @@ -0,0 +1,10 @@ | |||
| The Commands used in task1-4 are:- | |||
There was a problem hiding this comment.
Minor grammar and formatting nits.
- "task1-4" → "tasks 1–4"
- The trailing
:-is non-standard; prefer a simple:or a blank line followed by the list.
🧰 Tools
🪛 LanguageTool
[grammar] ~1-~1: Ensure spelling is correct
Context: The Commands used in task1-4 are:- 1-git init - -b can be us...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@2025/week-04-challenge/solution.md` at line 1, Update the heading text to use
proper grammar and formatting: replace the phrase "task1-4" with "tasks 1–4"
(use an en dash) and remove the non-standard ":-" suffix—either end the line
with a simple ":" or place a blank line after the heading before the list;
ensure the revised line reads something like "The Commands used in tasks 1–4:"
or the heading followed by a blank line and the list.
| 4-git push origin <branch name> | ||
| 5-git remote add origin "url of git repo" |
There was a problem hiding this comment.
git remote add origin must precede git push origin.
Step 5 (git remote add origin) is listed after step 4 (git push origin), but you can't push to a remote that doesn't exist yet. This ordering will cause errors and mislead learners following the guide sequentially.
📝 Suggested reordering
-1-git init
- - -b can be used for specific to add branch name for default one.
-2-git add <file name>
-3-git commit -m "commit message"
-4-git push origin <branch name>
-5-git remote add origin "url of git repo"
-6-git pull origin <branch name>
-7-git merge <branch name>
+1. git init
+ - Use `-b <branch-name>` to set the default branch name (e.g., `git init -b main`).
+2. git remote add origin <url of git repo>
+3. git add <file name>
+4. git commit -m "commit message"
+5. git push origin <branch name>
+6. git pull origin <branch name>
+7. git merge <branch name>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@2025/week-04-challenge/solution.md` around lines 7 - 8, The listed git steps
are out of order: "git push origin <branch name>" appears before "git remote add
origin ..."; update the sequence so git remote add origin "url of git repo"
comes before git push origin <branch name> (i.e., swap the two steps) to ensure
the remote exists before pushing.
2 participants
Summary by CodeRabbit
Documentation
Chores