Github - Tag - Dimas Maulana

Naming Conventions for Production Environments

Tue, 06 Jun 2023 06:47:00 +0700

Naming conventions are a crucial aspect of software development, providing consistency and clarity in various stages of the development lifecycle. In this article, we will explore the most common naming conventions for production environments, focusing on GitLab CI/CD, GitHub Actions, domain names, branch names, Docker Compose files, and Dockerfile names.

Naming	Common Convention
GitLab CI/CD Convention	prod
GitHub Actions Convention	prod
Domain Names	example.com
Branch Names	main/master
Docker Compose Files	docker-compose.yml
Dockerfile Names	Dockerfile

GitLab CI/CD Convention

In GitLab CI/CD, the convention for naming pipeline stages in production environments commonly involves using “prod” as the keyword. This convention ensures that pipeline stages are easily identifiable and aligned with the production deployment process.

Naming Conventions for Development Environments

Tue, 06 Jun 2023 06:45:00 +0700

Naming conventions play a vital role in software development environments, providing consistency and clarity throughout the development process. In this article, we will explore the most common naming conventions for development environments, covering GitLab CI/CD, GitHub Actions, domain names, branch names, Docker Compose files, and Dockerfile names.

Naming	Common Convention
GitLab CI/CD Convention	dev
GitHub Actions Convention	dev
Domain Names	dev.example.com
Branch Names	dev
Docker Compose Files	docker-compose.dev.yml
Dockerfile Names	Dockerfile.dev

GitLab CI/CD Convention

When working with GitLab CI/CD, the most common convention for naming pipeline stages in development environments is to use “dev” as the keyword. This convention ensures compatibility and alignment with GitLab CI/CD’s pipeline system.

Naming Conventions Stage vs Staging in Software Development

Tue, 06 Jun 2023 06:24:00 +0700

Naming conventions play a crucial role in software development, providing clarity and consistency in various aspects of the development lifecycle. When it comes to naming environments, such as staging, development, and production, there can be variations and debates around the usage of “stage” and “staging.” In this article, we’ll explore the differences and common practices surrounding these terms.

Defining Staging and Development Environments

Naming	Common Convention
GitLab CI/CD Convention	stage
GitHub Actions Convention	staging
Domain Names	staging.example.com
Branch Names	staging
Docker Compose Files	docker-compose.staging.yml
Dockerfile Names	Dockerfile.staging

Staging environments are integral to the software development process, serving as a dedicated space for testing and validation before deploying to production. In most cases, “staging” is commonly used as a noun to represent this environment. It refers to a stable and controlled testing area where developers can ensure their applications are functioning correctly and meet the required standards.

Categorizing GitHub Issues by Size and Pomodoro Estimation

Wed, 24 May 2023 10:17:00 +0700

Efficient project management is crucial for successful software development, and accurately estimating the size and duration of GitHub issues is a key component. By categorizing issues based on their size and estimating their duration using the Pomodoro Technique, development teams can effectively plan, prioritize, and allocate resources. This article explores a framework for categorizing GitHub issues into different sizes and provides guidelines for estimating their durations using Pomodoros.

Categorizing Issue Sizes

Issue Size	Description	Pomodoro Estimate
Tiny	Small and straightforward task	1 Pomodoro (25 minutes)
Small	Requires moderate effort and is relatively simple	2-4 Pomodoros (50 minutes to 2 hours)
Medium	Moderate effort, non-trivial task	4-8 Pomodoros (2 to 4 hours)
Large	Substantial effort, significant work	8-16 Pomodoros (4 to 8 hours)
X-Large	Major undertaking, complex features or systems	More than 16 Pomodoros (8+ hours)

To establish a common understanding within the development team, let’s use the following framework for categorizing GitHub issue sizes:

Translating the Eisenhower Priority Matrix into GitHub Priorities

Wed, 24 May 2023 09:52:00 +0700

The Eisenhower Priority Matrix is a popular tool for organizing tasks based on their importance and urgency. By categorizing tasks into four quadrants, it provides a visual representation of priorities. However, when it comes to managing tasks in a GitHub repository, it is useful to have a clear mapping of these priorities into default labels. In this article, we will explore how to translate the Eisenhower Priority Matrix into GitHub priority labels to effectively manage and prioritize tasks.

Clone Multiple Github Repositories With Different Deployment Keys But The Same Username

Fri, 05 May 2023 08:20:00 +0700

Cloning multiple GitHub repositories with different deployment keys can be useful when you need to access multiple repositories using different SSH keys associated with the same GitHub account. This guide provides step-by-step instructions on how to clone multiple repositories with different deployment keys while using the same username. By following these steps, you can streamline your workflow and manage multiple repositories more efficiently.

Step 1: Generate Deployment Keys

To begin, generate a deployment key for each repository you want to clone. Use the ssh-keygen command on your local machine to create a unique key for each repository.