Discover gists

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

VMDK to VHDX

Follow [steps][1]:

Download: http://download.microsoft.com/download/9/1/E/91E9F42C-3F1F-4AD9-92B7-8DD65DA3B0C2/mvmc_setup.msi (thanks @xavery)
Open Powershell as administrator and run Import-Module 'C:\Program Files\Microsoft Virtual Machine Converter\MvmcCmdlet.psd1'
And after ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath d:\scratch\vmx\VM-disk1.vmdk -VhdType DynamicHardDisk -VhdFormat vhdx -destination c:\vm-disk1

[Project Name]

Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase.

Project Context

[Brief description ]

[more description]
[more description]
[more description]

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

Clarify and agree on the scope of the system

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

	#!/bin/sh
	# script to automate the creation of chroot jail
	# w/ minimal executables to run git

	export CHROOT=/var/chroot

	function copy_binary() {
	for i in $(ldd $*\|grep -v dynamic\|cut -d " " -f 3\|sed 's/://'\|sort\|uniq)
	do
	cp --parents $i $CHROOT

	@if (@a==@b) @end /*
	@echo off & setlocal enabledelayedexpansion
	title nava.downloader.bat @ https://gist.github.com/a-sync

	if "%~1"=="/?" goto usage
	if %0 == "%~0" (
	set /p INPUT="nava.hu URL: "
	) else (
	set "INPUT=%~1"
	)

	@if (@a==@b) @end /*
	@echo off & setlocal
	title m3-downloader.bat @ https://gist.github.com/a-sync

	if "%~1"=="/?" goto usage
	if %0 == "%~0" (
	set /p INPUT="ID/URL: "
	) else (
	set "INPUT=%~1"
	)

	На некторых хостингах, в том числе хостинге beget, требуется явно указывать версию php для композера, так как версия php в консоли часто отличается от версии, заданной в контрольной панели для сайта.
	(Текущую версию php для консоли можно узнать командой php -v)
	Например, для версии 7.4 команда будет такая:
	composer-php7.4 install

	Для других версий php алиасы соответствующих версий будут такими:
	composer-php5.3
	composer-php5.4
	composer-php5.5
	composer-php5.6

	conda create -n ag python=3.11
	conda activate ag
	pip install autogenstudio
	autogenstudio ui --port 8081