in each ferry run, we're computing the diffs between the previous course and current course, and this record of each sync's changes is written as markdown files under data/change_log/. to get coursetable/coursetable#1852 up and running, we'd need to store diffs in the ferry db so that when we send out email alerts, we can specify which fields were changed
in each ferry run, we're computing the diffs between the previous course and current course, and this record of each sync's changes is written as markdown files under
data/change_log/. to get coursetable/coursetable#1852 up and running, we'd need to store diffs in the ferry db so that when we send out email alerts, we can specify which fields were changed