Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Liebranca116052d0. Pick a project if you haven't
1. Fork it if you haven't
2. Look for bugs, you can generally find them posted under "issues" or similar. Alternatively, use the program for a while until YOU find a bug or annoyance you'd like to work on
3. git checkout main
4. git reset --hard upstream/main
5. git reset clean -xdf
6. git pull upstream main
7. git checkout -b branch-name
8. Read the code to locate the issue. When you're new to a codebase, this is the hard part. You have to grep around a mountain of source files for what you're looking for and narrow down what the fuck you're supposed to be looking at
9. Write the patch
A. git add changed_files
B. git commit -m "Fix thing"
C. git push -u origin name-of-branch
D. Send a PR
E. Be patient
F. jmp 0x00 -
You're in luck. I happen to be the president of open-source. Here's my IBAN:
BE8323232323458790852
Related Rants
how to really contribute to open source?
question
open-source
contribution