My GitHub username is: ZunedKhan07
My name: Juned Khan
I recently received a temporary restriction on creating pull requests. This happened because I was working on two issues at the same time, which accidentally caused unrelated file changes to be included in one of my PRs. I understand this was not the correct workflow, and I sincerely apologize for the inconvenience caused.
Since then, I have carefully reviewed the contribution guidelines and the “how to open a pull request” guide. Moving forward, I will:
Work on only one issue per branch.
Keep commits small, clear, and focused.
Test all changes locally before submitting a PR.
Double-check that no unrelated files are modified.
I would be grateful if you could lift the temporary restriction so I can submit the updated PR. I truly value the opportunity to contribute to freeCodeCamp and will ensure this mistake does not happen again.
Thank you for your time and understanding,
Juned Khan
The issue with these pull requests was not that you changed other files, but that your changes did not appear to consider the actual issue at all.
The majority of our maintainers are people who generously volunteer their time to help keep our open source project running smoothly. Creating this sort of noise is incredibly disrespectful of their time.
Given this, I am not seeing a compelling reason to remove your contribution ban. If you have additional information you would like to share, please feel free to reply.
Thank you for taking the time to clarify the situation — I now understand that the real problem was not unrelated file changes, but that my PRs did not accurately address the issues they were linked to.
I want to sincerely apologise for this. I rushed to create multiple PRs in a single day without fully validating my changes against the actual requirements of the issues. In hindsight, I realise this created unnecessary noise and took valuable time from the maintainers — something I deeply regret.
Since then, I’ve taken a step back to reflect and learn:
I have re-read the contributing guidelines and understand the importance of submitting only well-tested, accurate fixes.
I will always ensure I understand the issue fully before starting work.
If I am unsure about the approach, I will confirm with a comment or discussion before opening a PR.
I truly value the opportunity to contribute to freeCodeCamp and to learn from such an experienced community. If given another chance, I will be more deliberate, respectful of the maintainers’ time, and focused on quality over speed.
Thank you for considering my request, and for the work you and the team do to guide contributors like me.
I’m sorry — I’m new to contributing, so I didn’t know about this rule. I had written my comment and then asked ChatGPT to help me modify it before sending it here. I understand now that this is not allowed. From now on, I’ll be very careful to follow all the guidelines and make sure this mistake doesn’t happen again. I truly appreciate your patience, and I’m really sorry for this oversight.
This is definitely much more compelling. However, I ask that you make a commitment here in this thread that you will not use AI to make future contributions - both on our forum here and to our codebase.
I understand, and I sincerely apologize for my mistakes.
I commit that from now on, I will not use AI content for any contributions.
All my future contributions will be written and reviewed by me personally. Thank you for giving me the chance to improve.
