DEV Community: Clarance Liberi 💯

Quick review on git commands

Clarance Liberi 💯 — Fri, 19 Mar 2021 13:13:29 +0000

In this blog, we are going to review some basic git commands. We are going to work through all essential git commands that you need to start working with git efficiently and productively.

Setting up git

After downloading and installing git bash you will need to set up this information so that git can start working properly but this will only be set once unless you re-install new git.

# - check git version
git --version

# - configure you Name and your email to identify yourself with Git
git config --global user.name "Your Name"
git config --global user.email "your@email.com"

Initializing/creating repository

in case you are creating new repository to track your file changes
you will need to use this command

# - initializing git repository
git init

Status [ of the repository]

when you want to see the status of the files in the repository, again in the current branch you will use this command which will show untracked files, etc.

# - show status of the repository
# - shows files which have been changed,
#   tracked, staged etc
git status

Stagging files

all about adding files to git repository, notice that you can use remove instead of add if you want to unstage files or remove files

# - staging :   adding files to stage area
# - staging area :  files that are going to be included 
#               in next commit


# - staging one file
git add file.js

# - staging multiple files
git add file.js file2.js file3.js

# - staging all files
git add .

Committing file [or stagging files]

saving changes you made in the repository.

# - commit : a term used for saving changes
#           to a repository

# - committing changes made from stagged files
# - '-m' means message , a message should be descriptive
# - showing what changes really made in the repository
git commit -m "Commit message"

History [of the repository]

list of necessary commands that you need to work through your git repository history.

# - view your commit history
git log

# - revert / go back to certain commit
# - '07e239f2f' is a sample commit id that we are
#   trying to go back on 
git checkout 07e239f2f

# - going back to the latest commit on 
#   the 'master' branch
git checkout master

Branches

list of commands that you will work with to interact with branches in the repository

# - Creating new branch
# - 'new-branch-name' is the name of the new branch
git branch new-branch-name

# - switching to branch in the repository
# - if branch 'branch-name' does not exists 
#   on the repository git will create it
git switch  branch-name

# - switch to any branch in the repository
# - 'master' is the branch we want to switch on
git checkout master


# - list all branch in the repository
git branch

#merge 'branch-name' to active branch   
git merge branch-name

# - delete branch
# - 'branch-name' is the branch we are deleting
git branch -d branch-name

Conclusion
All of these commands are super easy to work with as they are easily explained, with them you can start using GitHub or any other tool so that you can now control versions of your system, and I am pretty sure that it is a good note for those who already know git, Thank you

Tips to reproduce/fix bugs form software developers

Clarance Liberi 💯 — Sun, 06 Dec 2020 15:11:19 +0000

Tips to reproduce/fix bugs form software developers
We all know how hard it may be to google an error, some error tend to last too long due to not knowing how to search or find solutions for the error
here are a few tips

1. Use the meaningful text from the error

When you are going to search for an error on google try to pick only meaningful text from the error, and avoid timestamps, line numbers, name of files, or other stuff which maybe not that useful to the browser

2. Include names of the technology

While googling try to include names of the technologies like if you are using javascript, try to tag it in a search query, or if you are using a framework tag it

3. Small search query

Also, remember to minimize the search query as small text as possible but remember to keep it meaning full, keep in mind that the small text or phrase you write the more result you get on google so this can boost your search to more resources

4. First look at GitHub issues / StackOverflow posts

The reason why you need to first look at this platforms are, GitHub mostly have the solution of errors as they might have been reported early on the project so here you get a taste of solutions or alternative from the owners of the project, while StackOverflow is the world of words programmers problems

5. Be patient

googling errors does not mean that you have to always find a solution as you get your first search, No, sometimes you don't find a solution at the beginning and what you have to do is keep searching on other platforms not mandatory only Github or StackOverflow, give a try other platform and you may find it

6. Look around the community

at this step now look around your friends or elders who you may trust that they know something about the technology you are using,
they help you in one way or other so that your problem may be fixed

7. Refresh your mind and take a rest

programmers use their brain and butt than other things so they might be the time you are tired or anything else, first do something to refresh your mind or sleep like 1 hour then you will come back with good thinking than before

Trace where the function was called from, in javascript

Clarance Liberi 💯 — Thu, 01 Oct 2020 11:08:30 +0000

Hello, Today we are going to remind ourselves how we can trace a function so that we can know where it was called from. If you have not ever messed up while trying to find where a function was called from you can't understand how important this post is, but if you have messed up and struggled to know and find where exactly the function is called from and then here is the solution

so we already know some debugging functions in javascript like console.log()
but there is time they never help to such situation, that's when you find that the real thing to use is



console.trace()

so here is the step by step of doing the things

I am using CodePen for writing these simple codes

let us suppose we have two functions add and consoleAdd

and I think you have noticed that in add() function we have something called console.trace() so at this time we want to ensure and know where exactly add() function was called from.

so to know this we will go in console in browser dev tools, as where every console functions are found, so what you will see is the list of where the function is going called and there parents function
but the exact function will be the first one as you see right here

it thinks you already see that we have add in the first place so that's where our console.trace() was called from , but remember our aim is not knowing where console.trace() was called from but where add() was called from

simple console.trace() shows every function call from where console.trace() is called to the last one
I think you can see it clear in the above image that

console.trace() was called in add()
add() was called from consoleAdd()
and finally consoleAdd() was called by anonymous as it was called by browser while running the code

simple those number on the end of the name of a function are the number of the line where the function is returned or if the function did not return anything they take the next line to the last function curry brace }

and that 5 you saw, is the output of add(2,3)

I hope this post help, Thank you dev community