After sharing a post on CSDN titled “The Most Inspiring Computer Self-study course on GitHub”, someone commented, “I am a contributor to this project”. You can feel the strong sense of pride in this simple comment. Especially this warehouse has already harvested 140K + STAR. Speaking of this, I suddenly had a taste of lemon in my stomach.

To put it bluntly, once you become a contributor to a good open source project, it pays to brag about it or put it on your resume.

If you’re new to GitHub, don’t worry, I’ve put together a guide for you to get started. Click the link below.

GitHub is used by liberal arts girls, so why are you an engineering student

After getting started, you can take my tender hand and become a contributor to quality open source projects together! I promise, it will be fun 🙂

01. Fork Project

Personally, I like two open source projects most, one is my friend Jiangnan Dianyu micro personnel, and the other is my friend Macrozheng’s e-commerce project. You can also choose your own favorite, I take micro personnel here for example.

github.com/lenve/vhr

Click the link above to jump to the project’s home page, then click the Fork button on the upper right.

This action will copy the item to your personal account.

02. Clone Project

Now clone your fork items to the machine as follows.

PS: You must clone the fork instead of the original project, otherwise you have no permission to make changes.

Click on the green “Code” button and select “Open with GitHub Desktop”.

In the window that is displayed, select Open GitHub desktop. app.

Then jump to GitHub desktop and click “Clone.”

Wait a little while, it may be slow, but don’t be impatient, after all, you know. Click “Continue” when the following prompt appears asking you what you are doing with the project, being a contributor, of course.

The project is then smoothly cloned onto your computer.

03. Create a branch

Now, to create a Branch, click “Current Branch” and then click “New Branch” on the pop-up menu.

After filling in a Branch name you like, click “Create Branch”.

04. Make any necessary changes and submit them

First, I have communicated with Jiangnan Yiyu in advance, so I can directly edit his readme.md.

If you want to become a micro contributor, you can try to complete some unfinished features in your project and then submit a PR to become a contributor.

Once you save the modified readme.md, you can see the changes on the GitHub desktop.

After filling in the summary field, click “Commit to Itwanger-Add”.

You can see that the changes have been committed at the bottom of the GitHub desktop version.

Publish branches and create PR

Click “Publish Branch” to Publish the branch.

After publishing, you can see that the button changes to “Create Pull Request.”

Here is an explanation of “Pull Request” (PR for short). Here is an explanation from beepony, which I think is very clear.

Think about the exams we took in high school. Your test paper is like a warehouse, and your test paper is bound to have some errors, the equivalent of bugs in the program. When the teacher brings in your papers, it’s equivalent to forking them first. Make some revision notes on your paper, equivalent to committing. I’m going to pull a request, and I’m going to correct my mistakes.

Or to put it bluntly:

I changed jiangnan a little rain (called Songge) code, songge you pull back to see it!!

Once PR is explained, let’s click on “Create Pull Request” and it opens a page that prompts me to log in.

After login, you can see the PR we want to submit on the web page.

Click on the “Create Pull Request” button to jump to the next page.

To save time, I went straight to Songo.

Refresh the current PR to see that the PR has been merged successfully.

Answer the project home page and you will see that I have become a contributor. How happy I am!

From now on, I can also go out bragging force, Silent King 2, GitHub star 19.2K project contributor. Oh, it’s a great feeling. It’s like a yellow robe. No, no, no, it’s like a badge of honor!

Get moving!

PS: Post the GitHub link for the JavaBooks mentioned in this article to help you out.

Github.com/itwanger/Ja…