Ahmed Nagi nagi1

Rules to write a better commit message

These are my preferences for a good commit message, feel free to fork this gist and add your own standards, or add comment here to share yours with the community.

1. Include only the files related to the feature you are implementing:

Don't add any file that is not related to the main issue, you can make it in a separate commit.
Separating files that not related is important in the revert cases.
Revise the whole changes always before committing and make sure to mention each change you made in the message.

2. Commit subject should be concise and reflect the essence of the commit:

Imagine the commit as an Email to the owner or your team mates.
Subject in the first and main sentence of the commit, it should be concise and to the point.
It shouldn't exceed 50 char.

How to have specific .gitignore for each git branch

Objective

My objective is to have some production files ignored on specific branches. Git doesn't allow to do it.

Solution

My solution is to make a general .gitignore file and add .gitignore.branch_name files for the branches I want to add specific file exclusion. I'll use post-checkout hook to copy those .gitignore.branch_name in place of .git/info/exclude each time I go to the branch with git checkout branch_name.

	@servers(['web' => $user.'@'.$host,'localhost' => '127.0.0.1'])

	@setup
	// Sanity checks
	if (empty($host)) {
	exit('ERROR: $host var empty or not defined');
	}
	if (empty($user)) {
	exit('ERROR: $user var empty or not defined');
	}

	image: php:7.4-fpm

	definitions:
	steps:
	- step: &composer-install
	name: Build PHP
	caches:
	- composer
	script:
	- ls -al