DEV Community: Arnavbagchi

Basics of Git, Explained (Part 2)

Arnavbagchi — Thu, 09 Apr 2020 06:26:14 +0000

So in my last blog i discussed about initialising a git repository and making a first commit. Today we shall discuss about working with a remote repository through git.

Before we get started, we have to configure our user information in the local machine so that the git can keep a record of who is making the changes.

1.CONFIGURE USER

We will configure our username and our email by entering the following commands:

$ git config --global user.name "[your-username]"
$ git config --global user.email "[email address]"

for example

$ git config --global user.name "thewires2"
$ git config --global user.email "arnavbagchi04@gmail.com"

2.MAKE CHANGES

Now that our username is configured, we are ready to start working with git. We will first see a few useful commands to make user your commit is done properly before pushing it to a remote repository

$ git status

The git status command displays the state of the working directory and the staging area showing us which files have been staged and which files haven't. The status command does NOT show any information about the committed project history.

$ git diff

This is a highly useful command which shows us all the file differences that are not yet staged. To exit the diff command press Q

$ git add [file name]

This command is used to stage all the current changes in the file so that its snapshot will be taken in preparation for versioning.

$ git diff --staged

Use this command to see the difference between staging and the last file version

$ git reset [file name]

Another highly useful command, it unstages the currently staged file but it does not change any contents of the file itself.

After all the stages have been staged, we commit the changes with a good descriptive message of what changes have been made in the commit. I have discussed on how to make a commit in my previous blog. Now that the commit has been created in the local repository, we want to push the changes to our remote repository.

3.ADDING A REMOTE

Now we want to add a remote repository. We will require the URL of the remote repository and we will also have to name the remote. By convention, the remote repository is named as origin. Usually the remote URL is a github/bitbucket repo link.

$ git add remote <remote name> <repo link>

for example

$ git add remote origin https://github.com/thewires2/Django_Project

The above given example is a django project which i am working on my local machine and i push the code to the remote github repo so that my partners can see the changes.

4.PUSHING TO REMOTE REPOSITORY

Now we shall push the files/commits to our remote repository.This shall include all the changes that have been committed in the local repository.

$ git push origin master

Here the name of our remote repository is origin as we previously named it. Master is the main branch of the git repository in which the final changes are committed.

There you go! You have successfully pushed your code to the remote repository!

5.PULLING FROM REMOTE REPOSITORY

Now suppose that your friend wants to download the remote git repository.
They will have have to initialise a an empty git repository and add the remote as shown above.
Now its a simple pull from the remote :)

$ git pull <remote name> <branch name>
$ git pull origin master

The committed changes can be viewed by using the git log command.There we go! We have successfully pushed and pulled a remote repository!

I will be discussing about branches with emphasis on rebase in my next blog post. Till then, Ciao!

Hey there !
I am Arnav , an engineering student hailing from Mumbai.

#100DaysofCode

Arnavbagchi — Sat, 28 Mar 2020 16:50:06 +0000

As the title mentions, i will be starting the 100 days of code challenge during the period when my college has gone for an infinite shutdown. I will be laying out the rules in this challenge and i will try to follow them to the letter. I hope i am successful in this endeavour. I will be posting here everyday and also on twitter using the hashtag of 100 days of code.

As Geoff Stevens says in this blog post " Not everyone succeeds in completing the challenge. It takes determination, perseverance, and grit. Thoughtful planning plays a role, too."

I will be modifying the rules slightly to make use of my plenty of free time. I will state what i have changed below.As stated by Geoff in his blog the first and foremost tip for survival in this challenge is a public commitment. This shall be my public commitment . Another rule is that tutorials don't count as code. Code is should not be consumed but created. The rules state that if you miss a day it shall be added to the remaining days but it sets up a dangerous precedent for skipping days.

I will be coding for at least 4 hours a day from 10 p.m to 2 a.m. As mentioned previously, this does not include any tutorials. I will be maintaining a regular journal with my progress report of each day. I will be starting this challenge from the 30th of March , 2020.

Another important point about this challenge is burnout. Many aspiring developers try to code too much during the early days and end up quitting midway. This challenge is for increasing your patience, resilience, determination and most importantly, your coding skills.

I have a rough idea of the coding skills i want to achieve mastery in but i will be uploading a detailed plan soon.

Till the next time, Ciao !

Hello there!
I am Arnav , an engineering student hailing from Mumbai.

My Twitter!

Basics of Git , Explained .

Arnavbagchi — Fri, 20 Mar 2020 05:41:41 +0000

I am going to be talking about the basics of version control using git in this blog. Version control allows you to store the different versions of a project when it is under development. For example - You add a new feature to your project but it does not work out. Git allows you to restore the previous version of the project which was working properly.

It is especially helpful when working on large projects and it has advanced tools to help teams collaborate.

Installing git is a very simple task in Linux

$ sudo apt install git-all

You will need to configure git once its installed.

Initialising a repository

Create a simple python file which prints Hello World and store it into an empty directory called practice

Enter the directory in the terminal and initialise a repository using the command

$ git init

Checking Status

Before we do anything further we shall look at the project's status using the command

$ git status

Master is the main branch of the project.

Adding files to the repo

In the next step we shall add the python file and check the projects status again using the commands

$ git add .
$ git status

Making a commit

Lastly but most importantly , we will commit the python file to our repo using the command

$ git commit

When we enter this command , git will ask us to write a message for the commit stating whats its function. We will write First commit as our message

After committing the changes we will look at the status of our project again using

$ git status

Reversing a commit

We shall add another line print("abc") to our original file

Now we shall check status of project

We shall now follow all the commands given above on how to make a commit

$ git add .
$ git commit
$ git status

Now say we want to revert the changes and have the previous state of the file. We will use the checkout command to revert the project back to its previous stage.

$ git revert (commit hash)

These were the basics to getting started with version control , i will be making more detailed blogs in future posts.

Hey there !
I am Arnav , an engineering student hailing from Mumbai.

Best Python Books to get started.

Arnavbagchi — Wed, 18 Mar 2020 15:59:07 +0000

So i have started on the journey to become a coder myself quite recently. I had access to a lot of reference materials and therefore had the luxury of going through them all before opting to select these few. I genuinely believe that these books are the best way to get started on your coding journey.

Python Crash Course, 2nd Edition: A Hands-On, Project-Based
Introduction to Programming

This is an excellent book by the publishers No-starch press.They cover the basics thoroughly and are quite lucid in their explanations.As usual with these beginner books , they dont assume that the reader has any previous knowledge of python. The best part of the book is undoubtedly the projects. At the part of the book there are projects like an alien invasion game using pygame and data visualisation using libraries like matplotlib.

Python Playground: Geeky Projects for the Curious Programmer

Another book by the same publisher i.e No-starch press , this book expands on the previous topics of some superb real world projects. Getting a step by step guide with explanations is hugely satisfying . It is a definite recommend and a highly enjoyable book especially for newbies to the python coding world.

Think Python How to Think Like a Computer Scientist

This would be my last recommend for this post. Another excellent python book , this time by the Green Tea Press , this a thorough and serious book of the basics of python. It is the complete python manual for beginners and a must read to get your foundations built on a strong note.

Hey there!
I am Arnav , a Second Year Computer Science engineering student hailing from Mumbai.

Twitter : @potatoandchipss
Github : https://github.com/thewires2