3 ms·
I think that way to say that is open a PR, and just let it sit open. Eventually the repo owner will either merge it, close it, or sometimes ask you to do someth
by puffoflogic 4y ago
I think that way to say that is open a PR, and just let it sit open. Eventually the repo owner will either merge it, close it, or sometimes ask you to do something to it. In the last case, I often just politely decline. It's the flip side of the idea that publishing an open source project doesn't obligate you to support it — likewise, submitting a PR to a project doesn't obligate you to do any more work on it.
- adhesive_wombat 4y agoRight, but the point is I don't want the maintainer to avoid or delay handling it because they would like to change something, but either don't want to offend or don't want to go through the tedious rigamarole of editing the file as they want by using the ensemble of GitHub, the Internet, me and my text editor as a very slow and inefficient text editor (especially as I probably don't understand all their comments at first because they know the system inside out, and I don't). It's not that I will refuse to make changes, I will, within reason, it's that I'm also fine with the maintainer just taking over at any point and finishing it however they want, without any further back-and-forth. And I don't even care whose name is on it.