Browse good first issues to start contributing to open source

Re:Browse good first issues to start contributing to open so... by gus_massa on Wednesday January 22, 2020 @09:03PM (#22124150)

When there is an issue with a clear bug report that can be fixed in on of two lines and the solution is very clear, I like to answer something like:

"Thanks for the report! The problem is in link-to-file-in-GitHub. Do you want to send a PR to fix it? If not, we can fix it."

Sometimes they accept the proposal, sometimes not. It is a little more work to fetch the change, rebase, and merge it. But some people like the opportunity and perhaps may become a contributor in the future.

(If they don't accept, fix the problem soon and say thanks again with a link to the fix in case they want to see the change.)

[ Parent | on HN ]

Re:Browse good first issues to start contributing to open so... by daffl on Thursday January 23, 2020 @03:34PM (#22131661)

A big challenge I'm seeing is when it comes to tests. Even though it is documented in the contribution guide and - I'd like to think - fairly easy to get running (Clone, `npm i`, `npm test`) many first time bug-fixes or features do not include tests.

[ Parent | on HN ]