{"uri":"https://octothorp.es/","term":"git","thorpes":[{"uri":"https://justatheory.com/2012/05/sqitch-plan/","title":"Sqitch Update: The Plan","description":"I gave my first presentation on Sqitch at PGCon last week. The slides are on Slideshare and the PGCon site. It came together at the last minute, naturally. I was not able to pay as close attention to PGCon sessions as I would have liked, as I was doing last minute hacking to get the deploy command working on PostgreSQL, and then writing the slides (which are based on the tutorial). I was pleased with the response, given that this is very much a project that is still under heavy development and available only as a very very early alpha. There was great discussion and feedback afterward, which I appreciate."},{"uri":"https://justatheory.com/2012/01/vcs-sql-change-management/","title":"VCS-Enabled SQL Change Management","description":"Some thoughts on how to use VCS history to determine what changes need to be deployed or reverted without relying on a configuration file."},{"uri":"https://justatheory.com/2009/04/bricolage-cvs-to-git/","title":"Migrating Bricolage CVS to Git","description":"Following a discussion on the Bricolage developers mail list, I started down the path last week of migrating the Bricolage Subversion repository to Git. This turned out to be much more work than I expected, but to the benefit of the project, I think. Since I had a lot of questions about how to do certain things and how Git thinks about certain things, I wanted to record what I worked out here over the course of a few entries. Maybe it will help you manage your migration to Git."},{"uri":"https://justatheory.com/2012/04/sqitch-draft/","title":"Sqitch — VCS-powered SQL Change Management","description":"Back in January, I wrote three posts outlining some ideas I had about a straight-forward, sane way of managing SQL change management. The idea revolved around specifying scripts to deploy and revert in a plan file, and generating that plan file from VCS history. I still feel pretty good about the ideas there, and work has agreed to let me write it and open-source it. Here is the first step making it happen. I call it “Sqitch.”"},{"uri":"https://justatheory.com/2012/01/sql-change-management-sans-redundancy/","title":"SQL Change Management Sans Duplication","description":"Here’s how I propose to eliminate the duplication of code between deploy and revert SQL change management scripts."},{"uri":"https://benji.dog/articles/git-config/","title":"| benji","description":"This may be overkill, but it works on my machine"}],"bookmarks":[]}