I moved a lot of files around (using git mv) in a new branch called "refactor_models_directory"
Ohad noted that this causes a loss of history for git log
$ git log app/models/concerns/taxonomix.rb
(ONLY TWO COMMITS)
Added extend ActiveSupport::Concerns to mixins
Moved files to folders /concerns or /services
However, if you add --follow, the history shows up
$ git log --follow app/models/concerns/taxonomix.rb
(ALL THE COMMITS)
Added extend ActiveSupport::Concerns to mixins
Moved files to folders /concerns or /services
filtered users include admins, except in taxonomy form where it is no longer relevant to select admin users.
Initial migration fixes for postgresql
Taxonomy (Orgs / Locations related fixes)
make sure that default join objects of taxonomy are RW
…
…
…
Regarding git blame, it appears to work OK, but the documentation says to add -M or -C (or multiples -C's)
$ git blame --help
-M|<num>|
Detect moved or copied lines within a file. When a commit moves or copies a block of lines (e.g. the original file has A and then B, and the commit changes it to B and then A), the traditional blame
algorithm notices only half of the movement and typically blames the lines that were moved up (i.e. B) to the parent and assigns blame to the lines that were moved down (i.e. A) to the child commit.
With this option, both groups of lines are blamed on the parent by running extra passes of inspection.
<num> is optional but it is the lower bound on the number of alphanumeric characters that git must detect as moving within a file for it to associate those lines with the parent commit.
-C|<num>|
In addition to -M, detect lines moved or copied from other files that were modified in the same commit. This is useful when you reorganize your program and move code around across files. When this
option is given twice, the command additionally looks for copies from other files in the commit that creates the file. When this option is given three times, the command additionally looks for copies
from other files in any commit.