Several years ago a consulting client started writing VBA for an in-Excel prototype and asked us how to get their VBA code into Github.
We gave them 25 lines of VBA code (listed below) as a stopgap. This code simply exported all their workbook's code to a designated folder whenever they saved their workbook. They could then use Github's Windows client to commit and push the VBA code to Github.
A few days later we asked about building a more comprehensive, push/pull mechanism, and they said, "We don't need it. This is good enough."
Since then, we've observed this to be true of many Data Analysts who are using Excel as a secondary tool and only write VBA sporadically. Although there are products that integrate source control into the VBA IDE, many Data Analysts are happy pairing our bare-bones, 25 line, 'on save' exporter with Github's Windows client for 'good enough' Github integration.
' 4 steps to take before this code will work: |