gas-github

Chrome-extension to manage Google Apps Script(GAS) code with github/github enterprise.

With this extension, you can manage your code in GAS editor, push code to a new created branch, pull from a repository/branch.

The extension does not use Google Drive API, so you don't need any google authentication. Moreover, this extension support Bound scripts.

1.Install

Install this extension from chrome web store.

2.Usage

After install, when you open GAS editor, a new button will appear to allow you to login to Github/Github Enterprise.

2.1.Login

Login to your Github/Github Enterprise account, with Two-factor authentication support.

Actually, this is not a login action, but to create the access token which will be used for the extension

Note: the access token will be stored in chrome.storage.sync(password will not be stored), if you take this as a security hole, pleast DO NOT use this extension.

2.2.Bind

After login, you can bind your GAS Project with Github repo and branch, or create a new one.

2.3.Manage

Manage your code with the similar Push and Pull.But there are something need to know before use it.

2.3.1.Create Repository/Branch

In Repo and Branch dropdown list, there is an option to Create new Repo and Branch.

New Repo will be created with init, mean's a default README.md.

2.3.2.Pull and Push

The PULL/PUSH is not actually the same as Github's PULL/PUSH, because GAS project does not have any git info, so what we can do is limited.

The differences are:

• Pull will fetch code form the bind Repository/Branch, and OVERWRITE to current GAS Project. There is no merge operation.
• Pull will create new file when the file only shows in Github.
  • v2.0.0 has supported the file deletion when old files do not exist in Github.
• Push will commit file changed, file added to Github, but not file deleted.
  • v2.0.0 has supportd to delete files on Github. Directory will be deleted when all files under the dir has been deleted.

Other points:

• A diff dialog will be shown before you confirm to Push or Pull.
• You can choose files to operate with in the diff dialog.
• Push must have a commit comment which will be added from the diff dialog.

2.3.2.1 Gist

For using Gist, select Using Gist in the Repo dropdown list, then Branch dropdown will changed to Gist. But since gist do not has a name, you need to select the id to specific which gist to sync(a tooltip will show description of the gist).

• If there is no gist, you can create one from the extension.
• The gist created from extension will be initialzated with a default init_by_gas_hub.html file, this will be delete when first time you push you code to gist.
• You can change the description when push.
• Same as sync to repo, only file added and file changed is supported.

2.4.Logout

You can logout from the extension's option page any time. After logout, the access token stored in extension will be deleted, but you will need to delete the token yourself from Github/Github Enterprise's settins page.

3.Features

• Support Push/Pull code between github and GAS
• Support sync code to public/secret Gist
• Support embedded script
• Support create github repo, branch from GAS IDE
• Support diff check when pull/push
• Support choose files to pull/push
• Support file changed/added/deleted/renamed
• Support commit comment when push
• Support Github and Github Enterprise
• Support two-factor authentication
• Support directory in Github(with slash in filename)
• Google Apps Script native ui

4.Support

please create an issue for any question or bug report.

5.Known issues

• .gs file which contains a function with the same name as the file will not work #18. (limited by GAS'S RPC)
• Can not push to a blank repo without a init commit. (limited by Github API)

PS: There is a similar extension for sync your AWS lambda code.