Secure Shell, sometimes referred to as Secure Socket Shell (SSH), is a protocol which allows you to connect securely to a remote computer or a server by using a text-based interface. OpenSSH is an an open source SSH tool—widely used for Linux distributions. The same OpenSSH tool is also supplied/packaged by default with Git and enables Git authentication via SSH protocol. A common example of this is GitHub authentication and workflows using SSH. Here’s a quick look at some common SSH commands.

The post Common OpenSSH Commands Reference appeared first on Automation Dojos.

Git is the most popular distributed version control system which is currently an actively maintained open-source project. Git supports many command-line tools and graphical user interfaces. Since there are many Git commands you can use, mastering Git takes time. The following set of commands are probably the most commonly used commands that you should know as you may use it quite frequently.

The post Common Git Commands Reference appeared first on Automation Dojos.

Using below procedure, you shall be able to setup SSH-Agent to run automatically whenever GitBash is launched on Windows. The ssh-agent process will continue to run until you log out, shut down your computer, or kill the process. Also you may need to add your SSH keys separately unless already loaded or available as per your config.

However the main advantage is that no duplicate SSH-Agent process will be created for successive / multiple Gitbash sessions.

The post How To Setup Automatic SSH-Agent for GitBash appeared first on Automation Dojos.

By default the GitBash prompt settings / configuration come from shell script called ‘git-prompt.sh’. This is usually hosted inside ‘profile.d’ directory inside the GitBash installation directory. The below described method only focusses on customizing the ‘GitBash’ prompt and NOT about customizing default ‘Bash’ prompt on Linux terminals.

The post How To Customize GitBash For Windows appeared first on Automation Dojos.

The ‘Git for Windows’ by default does not come with MSYS2 package manager called ‘Pacman’ and hence it is a limited version or subset of the MSYS2. Also the bash which supplied wih Git for Windows is not a full version of bash hence does not provide for full Linux environment. Given below is the easiest method (bullet 3 above) to enable package manager (Pacman) support for an existing Git for Windows installation.

The post How To Install Pacman For Git on Windows appeared first on Automation Dojos.