added networking task1

[unixsatyam]

this is not a solution just flexing my skills

Summary by CodeRabbit

• Documentation
  • Added three new documentation/example text files containing short placeholder content for review and demonstration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Three new plain text files were added: badcode.md, verybadcode.txt, and finecommit.txt, each containing a single line of text. No code, exports, APIs, or functional logic were modified.

Changes

Cohort / File(s)	Summary
New simple text files badcode.md, verybadcode.txt, finecommit.txt	Added three single-line files with plain text content ("this is bad code hello krimada", "this is very bad code btw i want to eat kheer today", "thisis fine code no issue found and ready to go in the production"). No code or API changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 I nibble a line, soft and light,
A tiny file hops into sight,
One phrase, one hop, a cheerful nod,
New text arrives — I celebrate the mod! 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title 'added networking task1' does not match the actual content, which adds three unrelated files (badcode.md, verybadcode.txt, finecommit.txt) with placeholder text, not a networking task.	Update the title to accurately describe the actual changes (e.g., 'Add sample text files for practice') or align the changeset with the stated networking task objective.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@badcode.md`:
- Line 1: The file contains only the placeholder line "this is bad code hello
krimada" and must be replaced or the PR closed; either close the PR if it was a
test, or edit badcode.md to remove that placeholder and add a real
networking-task solution (code, configuration, tests) plus clear documentation
and learning objectives; update the PR description to match the new content and
include usage instructions, expected output, and any commands to reproduce so
the repo receives educational, working material instead of placeholder text.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

PR does not contain meaningful content and should not be merged.

The file contains no actual code, documentation, or networking-related content despite the PR title indicating "networking task1". The single line of text provides no value to the repository. Additionally, your PR description states this is "not a solution" and is just "flexing skills", and even the filename acknowledges it as "bad code".

For a learning repository like 90DaysOfDevOps, contributions should provide educational value, working solutions, or meaningful documentation. Please either:

• Close this PR if it was created for testing purposes
• Replace the content with an actual networking task solution with proper documentation
• Provide meaningful code or learning material related to the stated objective

🤖 Prompt for AI Agents

In `@badcode.md` at line 1, The file contains only the placeholder line "this is
bad code hello krimada" and must be replaced or the PR closed; either close the
PR if it was a test, or edit badcode.md to remove that placeholder and add a
real networking-task solution (code, configuration, tests) plus clear
documentation and learning objectives; update the PR description to match the
new content and include usage instructions, expected output, and any commands to
reproduce so the repo receives educational, working material instead of
placeholder text.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@verybadcode.txt`:
- Line 1: Remove the extraneous file verybadcode.txt from the PR (or replace its
contents with a real networking task submission that includes code,
documentation, and examples) and update the PR title/description to accurately
reflect the changes; ensure the repository no longer contains placeholder/random
text and that any added file follows the repo's learning objectives and includes
clear technical content and rationale.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

This file should not be included in the PR.

The PR title indicates "networking task1," but this file contains no networking code, documentation, or relevant content. The random text adds no value to a DevOps learning repository and should be removed.

Additionally, your PR description states this is "not a solution" but "just flexing my skills." A skills demonstration should include actual code, documentation, or technical content—not placeholder text.

Recommendation: Close this PR or replace it with a legitimate networking task submission that aligns with the repository's learning objectives.

🧰 Tools

🪛 LanguageTool

[style] ~1-~1: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: this is very bad code btw i want to eat kheer today

(EN_WEAK_ADJECTIVE)

🤖 Prompt for AI Agents

In `@verybadcode.txt` at line 1, Remove the extraneous file verybadcode.txt from
the PR (or replace its contents with a real networking task submission that
includes code, documentation, and examples) and update the PR title/description
to accurately reflect the changes; ensure the repository no longer contains
placeholder/random text and that any added file follows the repo's learning
objectives and includes clear technical content and rationale.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@finecommit.txt`:
- Line 1: The user-facing sentence "thisis fine code no issue found and ready to
go in the production" contains spelling, spacing, punctuation and grammar
errors; update that literal string to a clear, professional sentence (for
example: "This is fine code; no issues were found, and it's ready for
production."), ensuring capitalization, spacing, and punctuation are fixed
wherever the original string appears.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix spelling and grammar in the sentence.

This looks like user-facing text; consider correcting it for clarity and professionalism (e.g., “This is fine code; no issues found, and it’s ready for production.”).

✍️ Proposed edit

-thisis fine code no issue found and ready to go in the production
+This is fine code; no issues found, and it’s ready for production.

📝 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

	thisis fine code no issue found and ready to go in the production
	This is fine code; no issues found, and it's ready for production.

🧰 Tools

🪛 LanguageTool

[grammar] ~1-~1: Ensure spelling is correct
Context: thisis fine code no issue found and ready to g...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🤖 Prompt for AI Agents

In `@finecommit.txt` at line 1, The user-facing sentence "thisis fine code no
issue found and ready to go in the production" contains spelling, spacing,
punctuation and grammar errors; update that literal string to a clear,
professional sentence (for example: "This is fine code; no issues were found,
and it's ready for production."), ensuring capitalization, spacing, and
punctuation are fixed wherever the original string appears.