foresight: A way to find major owners of files you have changed in your commit

foresight.sh

#!/usr/bin/env bash
set -e

function ADD_AUTHOR {
  local author_to_add=$1

  if ! [ -z "${author_to_add}" ]; then
    #add something to add people to review in your source repo
  fi

}

function CHECK_OWNERSHIP {
  local line=$1
  read -a input <<< "${line}"

  local size=${input[0]}
  local owned_lines=${input[1]}
  local author=${input[2]}
  local file_path=${input[3]}

  local ownership="$(bc -l <<< "scale=1; ($owned_lines/$size)*100")"
  local is_owner="$(bc -l <<< "$ownership>=20")"

  if [ $is_owner -eq 1 ]; then
    echo $author " owns: " $ownership " percent of " $file_path
    ADD_AUTHOR $author
  fi
}

function GET_EMAIL {
  while read data; do
    echo "$data" | grep -E -o "<\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,6}\b>"\
      | grep -E -o "\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,6}\b";
  done;
}

function PROCESS_FILE {
  local FILE_PATH=$1
  local FILE_SIZE="$(cat $(echo $FILE_PATH) | wc -l)"

  # Find the people with current ownership
  git blame --show-email HEAD~1 -- $1 2> /dev/null | GET_EMAIL | sort | uniq -c\
    | while read line; do CHECK_OWNERSHIP "$FILE_SIZE $line $FILE_PATH"; done
}

function FORESIGHT {
  echo "FORESIGHT!"
  echo "Looking into the past to save the future..."
  echo "-------------------------------------------"
  git diff-tree --no-commit-id --name-only -r HEAD \
    | while read line; do PROCESS_FILE "$line"; done | sort | uniq
  echo "-------------------------------------------"
  echo ""
}

Outputs the emails for each person with >20% ownership of any file in your commit. Involving these owners in communication about changes to files they own has been shown to reduce the number of bugs in research done by microsoft.

For further reading see:
https://www.microsoft.com/en-us/research/publication/the-influence-of-organizational-structure-on-software-quality-an-empirical-case-study/
https://www.microsoft.com/en-us/research/publication/dont-touch-my-code-examining-the-effects-of-ownership-on-software-quality/

just added a bit to check for who created the file and add pull them as well

To use Foresight you will need to source it in your env file

So if you are using zsh you would add . ~/path/to/foresight.sh to your .zshrc file.
Basically the same instructions for bash just in your .bashrc file.

Then you will have FORESIGHT as a command that you can run from your console!

Now a repo at: https://github.com/designfrontier/foresight/blob/master/README.md