Skip to content

Instantly share code, notes, and snippets.

View pizofreude's full-sized avatar
👏

Hafeez Pizofreude pizofreude

👏
View GitHub Profile
@pizofreude
pizofreude / TIL_20250417_VCS.md
Created April 17, 2025 15:47
All things VCS

Keeping Empty Folder

Both .gitkeep and .keep can be used to keep an empty directory in version control. However, the difference lies in how Git handles them.

.gitkeep is a file that tells Git to keep the directory it's in as a versioned entity. When you commit a .gitkeep file to a Git repository, Git will keep the directory it's in, even if it's empty.

.keep is a file that tells Git to keep the directory it's in as a versioned entity, but it's not as widely supported as .gitkeep. While both files achieve the same purpose, some Git versions may not recognize .keep as a valid file for keeping directories.

In general, it's recommended to use .gitkeep instead of .keep to ensure that your empty directories are kept in version control across different Git versions and platforms.

@pizofreude
pizofreude / TIL_20250417_TerraformArtifacts.md
Created April 17, 2025 17:10
Terraform Code Artifacts and Descriptions

Terraform Code Artifacts and Descriptions

  • providers.tf
    Description: The providers.tf file is used to configure and declare provider settings in Terraform. Providers enable Terraform to interact with cloud platforms (e.g., AWS, Azure, GCP) or other services. This file specifies provider versions, regions, and authentication methods.

  • variables.tf
    Description: The variables.tf file defines input variables for Terraform configurations. These variables allow parameterization of values like resource names, regions, or instance types, making configurations more reusable and dynamic.

  • outputs.tf
    Description: The outputs.tf file is used to expose the results of a Terraform run. It outputs values, such as IP addresses, URLs, or resource attributes, for use by other configurations, tools, or workflows.

@pizofreude
pizofreude / TIL_20250418_ProjectStatusIndicator.md
Created April 18, 2025 11:42
How to indicate project status in GitHub README

Indicating the project status in your README is a great way to communicate the current state of your project to potential collaborators, recruiters, or users. You can use a "Project Status" section near the top of your README to make this clear. Here’s how you can do it:

Examples for Indicating Project Status

1. Use a Badge (Preferred for Clear Visuals)

Including a badge is a common way to display project status. You can generate badges using services like shields.io. Here’s an example:

![Project Status](https://img.shields.io/badge/status-in--progress-yellow)