Google App脚本应该存储在像GitHub这样的版本控制中 [英] Should Google App Scripts be stored in version control like GitHub

问题描述

我对管理Google App脚本共享开发的最佳方式感到困惑。问题是编辑谷歌应用程序脚本是通过一个在线编辑器完成的，它有自己的版本控制，但就我所知，这与其他开发者没有共享。

所以建议的做法是，我们从该编辑空间复制并粘贴到本地硬文件中，然后插入我们选择的版本控制系统，然后当我们想要测试我们复制并粘贴到在线编辑器中的东西？看起来很麻烦，容易出错。

我看到一些人将他们的Google App脚本放在Github这样的地方：

https://github.com/peterneubauer/neo4j-google-apps-script

如果我们可以直接从git推送到Google App脚本，就像我们用Heroku一样，将是非常棒的。我真的很希望能够对我的应用程序脚本运行一系列单元测试...

解决方案

a href =http://code.google.com/p/google-apps-script-issues/issues/detail?id=217&q=version%20control&colspec=Stars%20Opened%20ID%20Type%20Status% 20Summary％20Component％20Ownerrel =noreferrer> 217 并发布 1959 。

更新：查看使用Apps脚本的高级开发流程

I am confused about the best way to manage shared development of Google App Scripts. The thing is that editing google app scripts is done through an online editor with its own version control in place, but that's not shared with other developers as far as I can tell.

So is the suggested practice that we copy and paste from that editing space into local hard files and then push into the version control system of our choice, and then when we want to test things we copy and paste things back into the online editor? Seems messy and error prone.

I see some people are putting their Google App Scripts in places like Github:

https://github.com/peterneubauer/neo4j-google-apps-script

Would be great it we could push directly from git to deploy on Google App Scripts the same way we do with Heroku. Would really like to be able to run a battery of unit tests against my App Scripts ...

解决方案

You can star issue 217 and issue 1959 if that is important to you.

Update: Take a look at Advanced Development Process with Apps Script

这篇关于Google App脚本应该存储在像GitHub这样的版本控制中的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！