Hey all! So I'm trying to understand some things about GitHub. I've gotten good at using terminal to commit and push / pull to my own repositories ...
For further actions, you may consider blocking this person and/or reporting abuse
There's several ways that you could try.
1) ask. Try contacting the owner and ask where/if you could help
2) find things that you miss in a project and implement that
3) there's issues. If you find a project with open issues, comment on an interesting issue and let them know you're interested in fixing that.
this suggestion actually inspires me out of massive repositories on that regarding volunteering for projects out of interests.Thanks.
Thanks for the suggestions :)
Don't worry, you're not missing anything obvious. It is sometimes a matter of guessing and asking the right questions. It's never totally clear.
People are usually okay with receiving speculative PRs that may fix something, as long as you're humble about it.
Ultimately it can take a while to get right. You can start with lower barrier things like documentation issues, just to get a feel for the flow.
You're always welcome to find projects to make PRs such as this one on behalf of DEV 😄
oh cool! I'll check that out too.
Thanks so much! That makes a lot of sense. I actually did a PR for a documentation issue. It was just a comma in the wrong place but made me trip over the sentence when I was trying to read it. They actually told me they weren’t going to merge it because it’s trivial and will probably end up getting changed again. I’m assuming that’s the type of people to stay away from.
Did my first pull request :) It was a comma that didn't need to be there.... but still lol.
What you can do is check the repo issues and see if there is something you can do :D
Thanks! From there how do I find the file that the issue is in?
That part's on you. Unit tests will help you sometimes, other times you'll have to trace the flow of execution yourself (or write tests), still other times grep is your best friend. But every situation is different and the only way to learn is by doing.
More on tests as documentation:
Avoid the Code Crawl by Reading Tests
Brandon Martinez
Without docs or good tests, it's going to be a matter of search, trial, and error, as Dian is saying.