1617875220
Git Commands You Can Use To Dig Through Your Git History
In this short article, we’ll be exploring some quick git commands that can help us in digging through our repositories’ history of commits. We’ll look at
- git log
- git shortlog
- git show
- git rev-list
#git #git-log #git-commands #git-history #aws
What is GEEK
Buddha Community
1617875220
Git Commands You Can Use To Dig Through Your Git History
In this short article, we’ll be exploring some quick git commands that can help us in digging through our repositories’ history of commits. We’ll look at
- git log
- git shortlog
- git show
- git rev-list
#git #git-log #git-commands #git-history #aws
1625631509
Examples of the dig command in Linux
Dig Command Line Options and Examples
Here is the frequently used command line options and example’s of dig command.
1. Basic Dig Command
A basic dig command accept domain name as command line parameter and prints Address record.
2. Query With Specific DNS Server
The default dig command queries to dns server configured on your system. For example, the Linux systems keep default DNS entry in /etc/resolv.conf.
3. Print Short Answer
Use +short command line option to print result in short form. This is basically useful with the shell scripting and other automation tasks.
4. Print Detailed but Specific Result
Use +noall with +answer to print detailed information but specific. This will print only answer section including few more details as a result.
#linux commands #command #dig #dig command #useful examples #linux
1604109000
Best Practices for Using Git
Git has become ubiquitous as the preferred version control system (VCS) used by developers. Using Git adds immense value especially for engineering teams where several developers work together since it becomes critical to have a system of integrating everyone’s code reliably.
But with every powerful tool, especially one that involves collaboration with others, it is better to establish conventions to follow lest we shoot ourselves in the foot.
At DeepSource, we’ve put together some guiding principles for our own team that make working with a VCS like Git easier. Here are 5 simple rules you can follow:
1. Make Clean, Single-Purpose Commits
Oftentimes programmers working on something get sidetracked into doing too many things when working on one particular thing — like when you are trying to fix one particular bug and you spot another one, and you can’t resist the urge to fix that as well. And another one. Soon, it snowballs and you end up with so many changes all going together in one commit.
This is problematic, and it is better to keep commits as small and focused as possible for many reasons, including:
- It makes it easier for other people in the team to look at your change, making code reviews more efficient.
- If the commit has to be rolled back completely, it’s far easier to do so.
- It’s straightforward to track these changes with your ticketing system.
Additionally, it helps you mentally parse changes you’ve made using git log.
#open source #git #git basics #git tools #git best practices #git tutorials #git commit
1593435300
Basic Git Commands you need to Master
In this part you will get familiar with some basic Git commands. At the end of this blog you will be able to perform certain task like
- Set up a folder as a Git repository
- Perform basic Git operations on your Git repository
These are those commands you must conquer
Basic Git Commands
- At any location on your computer, create a folder named git-test.
- Open this git-test folder in your favorite editor.
- Add a file named index.html to this folder, and add the following HTML code to this file:
<!DOCTYPE html>
<html>
<head></head>
<body>
<h1>Sab Batade Aapko</h1>
</body>
</html>
Initializing the folder as a Git repository
- Go to the git-test folder in your cmd window/terminal and type the following command at the prompt to initialize the folder as a Git repository:
git init
this command will make a file named .git
#github #git #basic-git-commands #git-commands #git-status
1597916460
7 Best Practices in GIT for Your Code Quality
There is no doubt that Git plays a significant role in software development. It allows developers to work on the same code base at the same time. Still, developers struggle for code quality. Why? They fail to follow git best practices. In this post, I will explain seven core best practices of Git and a Bonus Section.
1. Atomic Commit
Committing something to Git means that you have changed your code and want to save these changes as a new trusted version.
Version control systems will not limit you in how you commit your code.
- You can commit 1000 changes in one single commit.
- Commit all the dll and other dependencies
- Or you can check in broken code to your repository.
But is it good? Not quite.
Because you are compromising code quality, and it will take more time to review code. So overall, team productivity will be reduced. The best practice is to make an atomic commit.
When you do an atomic commit, you’re committing only one change. It might be across multiple files, but it’s one single change.
2. Clarity About What You Can (& Can’t) Commit
Many developers make some changes, then commit, then push. And I have seen many repositories with unwanted files like dll, pdf, etc.
You can ask two questions to yourself, before check-in your code into the repository
- Are you suppose to check-in all these files?
- Are they part of your source code?
You can simply use the .gitignore file to avoid unwanted files in the repository. If you are working on more then one repo, it’s easy to use a global .gitignore file (without adding or pushing). And .gitignore file adds clarity and helps you to keep your code clean. What you can commit, and it will automatically ignore the unwanted files like autogenerated files like .dll and .class, etc.
#git basics #git command #git ignore #git best practices #git tutorial for beginners #git tutorials