Skip to content

Feature update #497

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
yo-its-anas wants to merge 3 commits into from
Closed

Feature update #497

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
dab60dc
Initial commit: Add info.txt with introductory content
yo-its-anas Oct 13, 2025
bf89cf4
Feature update: Enhance info.txt with additional details
yo-its-anas Oct 13, 2025
b72d38c
Initial commit: Added solution
yo-its-anas Oct 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions 2025/git/01_Git_and_Github_Basics/week4-challenge/info.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Hello, This is a week 4 Git Challenge !!!
30 changes: 30 additions & 0 deletions 2025/git/01_Git_and_Github_Basics/week4-challenge/solution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# Solution to Git Basic Tasks

### Commands that I used:

```
git init → Initializes a repo in my local
git add info.txt → Stages a file to that repo
git commit -m "Message" → Final commit
git push -u origin main → Push commit to remote
git pull origin main → Verify/pull changes
git log → View commit history
git branch feature-update → Creates new branch
git switch <branch name> → Switching branches
```
Comment on lines +5 to +14
Copy link

@coderabbitai coderabbitai bot Oct 13, 2025

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Add a language hint to the fenced block.

The command list lacks a fence language, tripping MD040. Annotate it (e.g., bash) so tooling renders it properly.

As per static analysis hints, apply:

-```
+```bash
 git init                   → Initializes a repo in my local  
 git add info.txt           → Stages a file to that repo  
 git commit -m "Message"    → Final commit  
 git push -u origin main    → Push commit to remote  
 git pull origin main       → Verify/pull changes  
 git log                    → View commit history  
 git branch feature-update  → Creates new branch  
 git switch <branch name>   → Switching branches  

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 markdownlint-cli2 (0.18.1)</summary>

5-5: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

</details>

</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

In 2025/git/01_Git_and_Github_Basics/week4-challenge/solution.md lines 5-14, the
fenced code block lacks a language hint causing MD040; add a language identifier
(e.g., bash) immediately after the opening so the block starts withbash
and keep the existing content and closing ``` unchanged.


</details>

<!-- fingerprinting:phantom:triton:sabertoothed -->

<!-- This is an auto-generated comment by CodeRabbit -->


---

### Brief explanation on why branching strategies are important in collaborative development:

Comment on lines +3 to +19
Copy link

@coderabbitai coderabbitai bot Oct 13, 2025

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Fix heading hierarchy to avoid lint errors.

Line 3 jumps from # to ###, and Line 18 repeats the same. Adjust both to ## … so the document increments levels correctly.

As per static analysis hints, apply:

-### Commands that I used:
+## Commands that I used:

-### Brief explanation on why branching strategies are important in collaborative development:
+## Brief explanation on why branching strategies are important in collaborative development:
📝 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
### Commands that I used:
```
git init → Initializes a repo in my local
git add info.txt → Stages a file to that repo
git commit -m "Message" → Final commit
git push -u origin main → Push commit to remote
git pull origin main → Verify/pull changes
git log → View commit history
git branch feature-update → Creates new branch
git switch <branch name> → Switching branches
```
---
### Brief explanation on why branching strategies are important in collaborative development:
## Commands that I used:
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

3-3: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

5-5: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents 
In 2025/git/01_Git_and_Github_Basics/week4-challenge/solution.md around lines 3
to 19, the heading hierarchy is inconsistent (jumping from `#` to `###` and
repeating `###`), causing lint errors; change both `###` headings at those
locations to `##` so they correctly follow the top-level `#` and maintain proper
incremental heading levels, then save and re-run the linter to confirm the
errors are resolved.

- **Isolating features and bug fixes**
Creating a new branch rather than working on main/master helps avoid downtime for end users, allowing developers to work in a solo environment and pull changes after staging/testing.

- **Facilitating parallel development**
Allows multiple developers to write code on different features and collaborate efficiently.

- **Reducing merge conflicts**
Prevents conflicts when each developer works in a specified branch.

- **Enabling effective code reviews**
Makes it easier to review new features, updates, or commits before merging.