In the previous article, we discussed how to install and configure Git on your local system.
This article covers the most common day-to-day Git operations: initializing a Git repository, checking status, adding files, staging changes, and committing them — the essential building blocks for any Git workflow.
Why install Git Bash on local system
Installing Git Bash is essential if you plan to work with any Git-based source code repositories. Here’s why:
Work with Git Repositories: Whether it’s Azure Repos, GitHub, GitLab, or Bitbucket – if you want to clone a repo, pull the latest code, or push your changes, Git must be installed locally.
Command Line Access: Git Bash gives you a Unix-style terminal on Windows, which is especially useful for running Git commands and shell scripts smoothly.
Tool Integration: You can integrate Git with popular IDEs like Visual Studio Code, IntelliJ IDEA, Eclipse, or even Android Studio, enabling built-in source control features right inside your development environment.
Script & Automation Friendly: Automate common tasks (like builds or deployment) using shell scripts directly from Git Bash.
Consistency Across Teams: Ensures a consistent Git experience, especially in teams using a mix of Windows, macOS, and Linux.
When you start using Terraform in a test or POC environment, you can start with a single folder which contains your code, variables, environmental variables and all other required components. However, this approach would not work for a large scale deployment.
If you are planning to deploy your organization’s infrastructure or client infrastructure using Terraform , you need to create a strategy first. To create a strategy, you need to consider some best practices which can be incorporated in your Terraform architecture.
In this article, we will discuss some of the best practices and important points, which can be considered and adopted during the creation of Terraform architecture.
Subhro.blog 