Thematic has also relocated to git hub, where many wonderful projects host their code. Git hub has a fantastic help section with articles and tutorials on how to get started, but if you are not familiar with the command line, it may seem overwhelming
The command line is no longer required for the fundamental workflow because there are several GUIs available today for dealing with git. You must nonetheless comprehend what you are doing. This manual is intended for those of you who are seeking to understand the basics of git and how git hub functions without writing a single line of code.
Thematic has also moved to git hub, a website where many excellent projects host their source code. If you are unfamiliar with the command line, Git hub’s excellent help section with articles and videos on getting started may seem intimidating.
Due to the availability of numerous GUIs for working with git nowadays, the command line is no longer necessary for the basic workflow. Yet, you must be aware of what you are doing. This guide is for you if you want to learn fundamentals of git and how git hub works without creating a single line of code.
A little note on remote
Other repositories that Git is aware of are contacted. By default, cloning a repository saves the parent repository under the name origin, meaning that the origin on your PC repository will point to your individual Thematic fork on git hub. The names of the remote controls are completely up to you. If you wish to monitor the work of the other people who have also forked Thematic, you might add a remote.
Adding the Thematic git hub repository as a remote is one thing you must do if you want to stay up to date with the primary development. The naming standard for this remote is upstream.
Clone and fork
To begin with, we need a fork. Simply click the fork button in git hub to have your own private repository of Thematic copied to your git hub user account.
You need to clone your repository to your computer in order to begin working on it. As a result, you now have two repositories: one local on your computer and one remote on git hub.
Every repository on Git hub has the potential to allow for independent development, which is why the process is known as forking.
Establish a topic branch.
Tags and branches are used to organize Git repositories. To keep lines of development apart, use branches. With git, the master branch is typically the default. Topic branches are generally referred to as branches created off of the master.
When you are developing a website and have an idea, for instance, but worry that implementing it might break something, you might consider using branching. Make a branch for your concept, put your work in there, test it out, and then merge the branch back into master when everything functions as it should.
Another use case might involve comparing two concepts, such as two color palettes for your website. Create a branch for each concept.
-D.Jaya Deepika
Information Technology