Add latest version of Google Apps Scripts to GitHub

[aricforrest]

Overview

The Google Apps Scripts used by the website project should be added to the website git repository. This will allow version control and tracking of changes made to the App Scripts over time.

Action Items

• Obtain view access to wins-form (response) Sheet and gh-requests (Doc) in the admin Google drive share from a technical lead
• Install node.js and npm (if they are not already installed) on the local workstation
• Update your local gh-pages branch with upstream changes, then checkout a new issue branch
• edit .gitignore to add a line containing the filename .clasp.json, then run git add .gitignore
• Create a folder called "google-apps-scripts" in the root of the website repository.
• From within the "google-apps-scripts" folder, create a subfolder for each Apps Script project listed below. In each subfolder, execute the commands npm install clasp and npm install @types/google-apps-script
  • wins-form-responses
  • gh-requests
• From either of the above subfolders, execute the command clasp login, then authenticate to Google Drive and grant permissions to the clasp app
• In each subfolder, clone the script using the command clasp clone <ID> where the script ID can be found on the corresponding Projects Settings page in the Google Drive IDE, then use git add to add the following files to the new issue branch: Code.js, appsscript.json, package.json, package-lock.json
  • wins-form-responses
  • gh-requests
• run git commit, then push changes to your fork of gh-pages, then create PR in the usual manner.

Merge Team - Upon Completion

• Release dependency on Create wiki page "Hfla Google Apps Script Development/Review Process" #4134 and move that issue into the New Issue Approval column with "ready for dev lead" label.
• Remove developer's access to files in the Hfla Google Drive Admin folders.
• Regenerate the gh key using the instructions in the Wins Admin Guide.

Example folder structure:
├── google-apps-scripts
│   └── wins-form-responses
│         └── Code.js, appscript.json, package-lock.json, package.json

Resources

• Wins Admin Guide
• https://github.com/google/clasp

[Sebster3]

ETA: Monday 3/27 EOD
Availability 1-4PM Fri, 6-9PM Mon

[Sebster3]

I have a blocker on the following action items:

1. From either of the above subfolders, execute the command clasp login, then authenticate to Google Drive and grant permissions to the clasp app.

   I'm able to successfuly log into my personal google account (which has access to the HFLA Drive), however I wasn't asked specifically to provide access to the HFLA Drive—which the action item seems to imply should happen. Is it sufficient for clasp to be authenticated using my google account?

2. In each subfolder, clone the script using the command clasp clone <ID> where the script ID can be found on the corresponding Projects Settings page in the Google Drive IDE, then use git add to add the following files to the new issue branch: Code.js, appsscript.json, package.json, package-lock.json

   I'm not sure where to find the "Project Settings" page or anything resembling a script ID for the two files mentioned in the issue: wins-form-responses, gh-requests.

There's currently no active branch for this issue on my forked repo as the final action item consists of pushing the changes made in the previous steps.

Thanks in advance for the help!

[roslynwythe]

Hi @Sebster3 -
Thank you for taking up this issue. I'm not sure why you weren't asked to authorize clasp to access your Google Drive. Let's see what happens when you run the clone command. To get the project id, open the production Sheet (or Doc), then click Extensions..Apps Script, then click the Project Settings (gear) icon in the left column. The ID can be copied from the Project Settings page.

You should be working in a new issue branch created in Action Item #3. That branch will be pushed to a branch on your forked repo as the final action item.

[Sebster3]

Thanks for helping @roslynwythe! It looks like I'll need edit access to Wins-form (Responses) in Drive before I can access the Extensions menu. Also, the gh-requests file doesn't appear to have an Extensions menu, which could be a follow up problem after we sort out getting proper permissions on the first file.

[roslynwythe]

Thanks for helping @roslynwythe! It looks like I'll need edit access to Wins-form (Responses) in Drive before I can access the Extensions menu. Also, the gh-requests file doesn't appear to have an Extensions menu, which could be a follow up problem after we sort out getting proper permissions on the first file.

Permissions have been granted. You should now see an Extensions menu on gh-requests. Let me know if you don't.

[Sebster3]

Hm, the Extensions menu on wins form remains greyed out and there is no Extensions menu available on gh-requests.

I've sent edit requests directly from the files. hopefully that helps.

[Sebster3]

Thanks @roslynwythe! The recent set of permissions you provided got everything back on track and a PR is now open :)

#4365