Specify column renaming in your git commit message so Datafold can map renamed columns to their original counterparts in production for accurate comparison.
oldcol
to newcol
.
name
has been renamed to first_name
in the PR branch.
col1 > col2 > col3
) result in the final rename (col1 > col3
).col1 > col3
). Sequential renames (col1 > col2 > col3
) can also work, but specifying the final state simplifies understanding during review.Aspect | Git Commits | PR Comments |
---|---|---|
Tracking Changes | Tracks changes on a change-by-change basis. | Applies changes to the entire changeset. |
History Linearization | Linearizes history assuming merged branches introduce new changes on top of the base/current branch (1st parent). | N/A |
Chained Renames | Sequential renames (col1 > col2 > col3) result in the final rename (col1 > col3). | It’s best to specify the final result directly (col1 > col3). Sequential renames (col1 > col2 > col3) can also work, but specifying the final state simplifies understanding during review. |
Precedence | Renames specified in git commits are applied in sequence unless overridden by subsequent commits. | PR comments take precedence over renames specified in git commits if applied during the review process. |