{"push_id":839741215,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"e55b0181786bc86ece66b965038ace74f2b2735a","before":"36709cdf6988ee849ad3663ba977fa0500ad1990","commits":[{"sha":"f16ef66ef14a65286812a155e0214f58e65954cb","author":{"email":"b892f067921d231448e8f0a591107de8b2ad3202@sunbase.org","name":"Øyvind A. Holm"},"message":"Store contents from synced.sqlite as SQL in synced.sql instead\n\nHaving the file sync info in an in-repo SQLite database works fine, but\nit's merge hell. Executing \"std\" commands or anything else that modifies\nsynced.sqlite on branches while there are simultaneous changes on master\nalmost always results in conflicts and I'll have to dump to text files,\nedit and then import it back. Urgh. So instead, store the info in a flat\nSQL file which is simply a \"sort-sqlite synced.sqlite; sqlite3 .dump\n>synced.sql\". Makes life about 7.52% easier overall.\n\nThis commit does the following:\n\n- \"sqlite3 synced.sqlite .dump >synced.sql\"\n- \"git ignore synced.sqlite\", this adds synced.sqlite to .gitignore and\n  deletes it from Git.\n- Add \"sqlite3 synced.sqlite .dump >synced.sql\" to Makefile so it's\n  executed with \"make\". Should be done before commit when there are new\n  filesync changes.\n\n15842b22-7b02-11e5-91ef-fefdb24f8e10","distinct":true,"url":"https://api.github.com/repos/sunny256/utils/commits/f16ef66ef14a65286812a155e0214f58e65954cb"},{"sha":"e55b0181786bc86ece66b965038ace74f2b2735a","author":{"email":"b892f067921d231448e8f0a591107de8b2ad3202@sunbase.org","name":"Øyvind A. Holm"},"message":"Makefile: If synced.sqlite doesn't exist, create it from synced.sql\n\n203b462a-7b04-11e5-9d37-fefdb24f8e10","distinct":true,"url":"https://api.github.com/repos/sunny256/utils/commits/e55b0181786bc86ece66b965038ace74f2b2735a"}]}