Greentea

Using Git and GitHub

Git — source control system, repository — source code storage, GitHub — repository hosting.

First of all, it is recommended to download applications able to conveniently work with Git.

They learn how to commit individual lines of code instead of entire files and the principle of small commits (another article about microcommits).

image

What should I do if the entire file is displayed as changed?

image

Git Special Files

image

How to issue and send a patch to the project?

The GitHub system uses the pull request mechanism — first a fork is created — a copy of the repository — commits are made to it, and then the merge request is sent to the original repository.

To update the fork code to the current version of the target repository — at this time, the easiest solution is to remove the fork and recreate it. The removal is done in the fork settings in its Settings -> Delete this repository -> Entering the name of the repository.

Receiving and sending changes

Git allows you to store commits locally on the computer (the commit itself does not cause sending to the server), and send at any convenient time.

What if the sending fails?

You can also make changes to the code or wiki pages editing via the GitHub web interface by selecting the file and clicking the pencil icon.

See also: