Ideally, you’d also first talk to the developers in charge of the project to see if your changes would be wanted in the first place.
(Or you’d start by reviewing existing bug reports and feature requests and addressing one of those.)
What I mean is, it’s generally better to not just throw code at them and hope they’ll like it. If you check first to see if they want it, you can save yourself from wasting effort on writing code that they’ll decline.
I assume when people do that it’s because they’re going to be making the fork regardless, and they think they’re being helpful by submitting a pull request with thier AI slop… But really they should just keep it on thier own fork if they don’t understand the changes but want to use it regardless…
Ideally, you’d also first talk to the developers in charge of the project to see if your changes would be wanted in the first place.
(Or you’d start by reviewing existing bug reports and feature requests and addressing one of those.)
What I mean is, it’s generally better to not just throw code at them and hope they’ll like it. If you check first to see if they want it, you can save yourself from wasting effort on writing code that they’ll decline.
I assume when people do that it’s because they’re going to be making the fork regardless, and they think they’re being helpful by submitting a pull request with thier AI slop… But really they should just keep it on thier own fork if they don’t understand the changes but want to use it regardless…