See how a minor change to your commit message style can make a difference. Examples
Have a look at CLI util git-conventional-commits to ensure this conventions and generate changelogs
#!/usr/bin/env bash | |
# Exit on error. Append "|| true" if you expect an error. | |
set -o errexit | |
# Exit on error inside any functions or subshells. | |
set -o errtrace | |
# Do not allow use of undefined vars. Use ${VAR:-} to use an undefined VAR | |
set -o nounset | |
# Catch error in pipes | |
set -o pipefail |
See how a minor change to your commit message style can make a difference. Examples
Have a look at CLI util git-conventional-commits to ensure this conventions and generate changelogs
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.
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.
https://gist.github.com/aroraayush/7b001903885bd35b902269babe2ccea8
pip3 install pipenv
pipenv shell
Put this in .vimrc | |
``` | |
" Set PowerShell as shell | |
set shell=powershell.exe | |
set shellcmdflag=-NoProfile\ -NoLogo\ -NonInteractive\ -Command | |
set shellpipe=| | |
set shellredir=> | |
``` | |
Enable scripts in powershell | |
``` |
Start explorer in current folder
start .
Delete a folder recursively
rmdir /S <dir_name>
Enable scripts powershell
# --------------------------------------------------------------------------- | |
# | |
# Description: This file holds all my BASH configurations and aliases | |
# | |
# Sections: | |
# 1. Environment Configuration | |
# 2. Make Terminal Better (remapping defaults and adding functionality) | |
# 3. File and Folder Management | |
# 4. Searching | |
# 5. Process Management |