Cooldown appeal — submitted PRs before reading CONTRIBUTING.md #948
Replies: 1 comment
-
|
hi @Sagargupta16 I don't want to make any false accusations. It really saddens me that I can't talk to users who visit my repo without strong suspicion that I am conversing with a bot, or a bot who is being steered. I don't know anything about you except a few public facts. Here's what I can tell about you after a few minutes of observation. For the past few days you've been posting very frequently across github. In some cases, the issues/PRs look more authentic - in other cases they do not. In almost every case, you engage in extended back-and-forth with Copilot. The examples that you highlight on your profile are not flattering. It seems as though 4 days ago you opened issues/PRs on high-profile repos. I have not found one merged, although there is a 1-liner awaiting approval so good for you.
According to this, you made your very first PR only a week ago - firstcontributions/first-contributions#112840 - so I'm very impressed at your progress. Apparently this is what you've been doing all day: https://api.github.com/users/Sagargupta16/events - high-frequency, bursty activity across repos - including, unfortunately for you, mine. Although I have my own opinion, it's not my place to speculate. In fact, I would really be impressed if someone could get one of these highly train O*** C*** bots to produce something of worth, and then know the basics of how to submit it. I haven't the privilege of witnessing any such activity yet. Regarding this repo, I appreciate "your" candidness about not reading the CONTRIBUTING.md. I must assume, based on context, that you have probably never even visited this repo before. But any "genuine open-source contributor" would know that you do not submit a PR anywhere without reading the guidelines in the CONTRIBUTING doc. So I do not find this credible. If you wish to contribute to this repository, you may do so by sharing the resources that you are relying on to generate this activity - because those resources may actually be interesting and well-engineered. I am really not against O*** C*** per se - but I have yet to see it put to good use. So share your methodology - maybe it even demonstrates a clever use of claude code and the other thing that is awesome. Otherwise, go build something awesome, and I will find out about it. Or spend three months working on something and then you may submit again in 90 days, no sooner, and the project itself must be at least 90 days old. Or, if this is a bot, submit your own source code - it may be awesome. That's the end of it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @hesreallyhim,
I'm following the bot's suggestion to open a discussion since my issue was auto-closed.
I made a mistake: I submitted two PRs (#944, #945) to recommend resources without reading CONTRIBUTING.md first. I didn't know that PRs aren't accepted and that the web UI form is required. When the PRs were closed, I tried submitting via the issue template, which triggered the cooldown escalation.
I'm not a spammer — I'm a genuine open-source contributor (68+ repos, PRs to apache/airflow, stanfordnlp/dspy, chroma-core/chroma, awslabs/mcp, freeCodeCamp, TheAlgorithms, exercism, and more). I simply didn't read the rules before my first interaction, which I fully own as my mistake.
I understand the anti-spam measures exist for good reason and I respect the process. If the permanent restriction could be reconsidered at some point, I'd follow the CONTRIBUTING.md exactly — web UI form only, one submission at a time, under 500 characters.
If not, completely understood. Thank you for maintaining such a valuable resource for the Claude Code community.
Best,
Sagar Gupta (github.com/Sagargupta16)
Beta Was this translation helpful? Give feedback.
All reactions