I delete the extra files and change the name of my JSON file as same my github username.

[Hamidmirzapour]

I delete the extra files and change tha name of my json file as same mu github username. Please pull my request.

[zero-to-mastery-bot]

🙏 Thanks for your pull request @Hamidmirzapour, The team will now review and merge this request. In the mean time why not check out some of the other opensource projects available, contributions are greatly appreciated!

Some of the most popular are

• Student Resources
• ZTM Job Board
• Complete Web Developer Manual

---

PR Statistics

#️⃣ PR Number:	➕ Line Additions:	🗑️ Line Deletions:
2864	16	0

📑 Files Changed:	⭐ Repo Stars:	🔱 Total Forks:
1	935	2597

[zero-to-mastery-bot]

🙏 Thanks for your pull request @Hamidmirzapour, The team will now review and merge this request. In the mean time why not check out some of the other opensource projects available, contributions are greatly appreciated!

Some of the most popular are

• Student Resources
• ZTM Job Board
• Complete Web Developer Manual

---

PR Statistics

#️⃣ PR Number:	➕ Line Additions:	🗑️ Line Deletions:
2864	16	0

📑 Files Changed:	⭐ Repo Stars:	🔱 Total Forks:
1	935	2599

[zero-to-mastery-bot]

🙏 Thanks for your pull request @Hamidmirzapour, The team will now review and merge this request. In the mean time why not check out some of the other opensource projects available, contributions are greatly appreciated!

Some of the most popular are

• Student Resources
• ZTM Job Board
• Complete Web Developer Manual

---

PR Statistics

#️⃣ PR Number:	➕ Line Additions:	🗑️ Line Deletions:
2864	16	0

📑 Files Changed:	⭐ Repo Stars:	🔱 Total Forks:
1	935	2599

[Hamidmirzapour]

Please accept my pull request and merge my commits to main branch.

Thanks a lot.

[Hamidmirzapour]

@dga Please check my request.

[ProsperousHeart]

You appear to have conflicting files. I assume because you created a 2nd PR. Your original PR was already approved and does not look like this file.

You have 2 options:

1. close this PR as your original one was the right one (ignoring the changes of this 2nd PR)
2. pull down the main branch, merge into yours & fix issues, then push changes back up

[zero-to-mastery-bot]

⚠️ MERGE CONFLICT DETECTED!

@Hamidmirzapour A possible conflict has been detected, you will need to resolve this before your pull request can be merged. The most common reason conflicts occur, is when the contributor does not run git pull origin master before pushing their new changes.

Before we can merge the code, you will need to resolve the conflict, check out these videos by Aldo: How To Get Started With Open Source and How To Resolve Git Merge Conflicts. If you get stuck ask over on Discord.

[zero-to-mastery-bot]

⚠️ MERGE CONFLICT DETECTED!

@Hamidmirzapour A possible conflict has been detected, you will need to resolve this before your pull request can be merged. The most common reason conflicts occur, is when the contributor does not run git pull origin master before pushing their new changes.

Before we can merge the code, you will need to resolve the conflict, check out these videos by Aldo: How To Get Started With Open Source and How To Resolve Git Merge Conflicts. If you get stuck ask over on Discord.

[zero-to-mastery-bot]

⚠️ MERGE CONFLICT DETECTED!

@Hamidmirzapour A possible conflict has been detected, you will need to resolve this before your pull request can be merged. The most common reason conflicts occur, is when the contributor does not run git pull origin master before pushing their new changes.

Before we can merge the code, you will need to resolve the conflict, check out these videos by Aldo: How To Get Started With Open Source and How To Resolve Git Merge Conflicts. If you get stuck ask over on Discord.