Dev ops challege

[Mustansar60]

Summary by CodeRabbit

• Documentation
  • Added a new Week 3 Git Challenge section to the documentation.
  • Updated the DevOps community challenge description with refreshed timeline details.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

Minimal documentation updates across two README files: addition of a "Week 3 Challenge on Git" header to 2025/git/README.md, and removal of a specific date reference from the main README's DevOps challenge description.

Changes

Cohort / File(s)	Summary
Git README Header 2025/git/README.md	Added new top-level markdown header "## Week 3 Challenge on Git"
Main README Phrasing README.md	Removed explicit start date "on January 1st, 2023" and rephrased DevOps community challenge sentence for temporal generality

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• LondheShubham153/90DaysOfDevOps#373: Directly related as both PRs modify the same file 2025/git/README.md with competing changes (main PR edits content while retrieved PR deletes it).

Suggested reviewers

• LondheShubham153

Poem

Hop, hop! New headers bright and bold,
🐰 Dates removed to make stories untold,
README's dance, a gentle refrain,
Documentation flows like morning rain! 📝✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Dev ops challege' is vague and contains a typo ('challege' instead of 'challenge'). It does not clearly convey what the pull request actually changes.	Revise the title to be more specific and descriptive of the main changes, such as 'Update README with Week 3 Git challenge and remove hardcoded date' and fix the spelling of 'challenge'.

✅ 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.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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: 0

🧹 Nitpick comments (1)

README.md (1)

5-5: Minor wording clarity issue.

The phrase "challenge starting and embark" is slightly awkward and could be clearer. Consider revising to something like: "Join our DevOps community challenge and embark on a 90-day journey..." or "Join our DevOps community challenge starting now and embark on a 90-day journey..." to improve readability.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4c3f0ea and 3dc9403.

📒 Files selected for processing (2)

• 2025/git/README.md
• README.md

🔇 Additional comments (1)

2025/git/README.md (1)

1-1: Clear and appropriate section header.

The markdown header is well-formatted and provides a clear title for the Git challenge content.