Concern: Same issues being opened multiple times & closed after PR submission

[yachikadev]

Hi @Priyanshu-byte-coder and fellow contributors,

I hope everyone is doing well! I wanted to bring up something that has been affecting many contributors here and I think genuinely needs attention.

I've noticed that contributor @tmdeveloper007 has been repeatedly opening duplicate issues on the exact same topics. Here's the proof:

Topic	Duplicate Issues
test: add unit tests for csv.ts	#2851, #2895, #2922
test: add unit tests for achievement-estimators	#2721, #2794, #2921
test: add unit tests for streak calculation	#2771, #2795

The same issue is being opened 2 to 3 times. Contributors like me then spend real time understanding the problem, setting up the codebase, writing code, and submitting a PR — only to find the issue has been closed by the owner shortly after, with no explanation.

This is genuinely discouraging because:

• Our time and effort goes completely to waste
• There is no communication about why the issue was closed
• It creates confusion about which issues are actually valid to work on

This is especially tough during GSSoC, where contributors are working hard to make meaningful contributions.

I’m not raising this to point fingers — I just want to make the contribution experience fair and better for everyone. It would really help if maintainers could:

1. Screen issues for duplicates before approving or assigning them
2. Avoid closing issues when a PR has already been submitted against them
3. Leave a comment explaining the reason if an issue needs to be closed

I believe this repo has a great community and I’d love to see it become even more contributor-friendly. Thank you for taking the time to read this!

[Priyanshu-byte-coder]

Thanks for raising this ,the concern is valid and we have taken action.

What we found:

The contributor in question opened 50 issues and 50 PRs in 7 days, many of which were duplicates of each other. For example, "unit tests for crypto.ts" appeared as issues #2989, #3008, and #3028 with corresponding duplicate PRs. Several recent PRs contained no code changes at all ,just a single comment line added to existing test files.

What we have done:

1. Closed all duplicate issues and PRs. Only one issue/PR per topic remains open where applicable. Issues for modules that already have tests in main have been closed.

2. Added issue templates with a required duplicate-check checkbox. Contributors must confirm they searched existing issues before opening a new one.

3. Added an automated duplicate detection workflow that will auto-close new issues if an existing issue for the same test topic already exists.

Going forward:

• One issue per topic. Duplicates will be closed immediately.
• PRs must contain meaningful code changes. Adding only comments does not count.
• Repeated abuse will result in a temporary block.

We value every contributor's time and want GSSoC to be fair for everyone. If you spot more duplicates or gaming, tag the maintainer directly.