The .clasp.json files contain the GAS project IDs only accessible inside Google. (example)
However, people using clasp CLI to push to their GAS project ID will need to overwrite these files.
What I think it might be better in either way:
add .clasp.json in .gitignore file but it will not work since this file is required for your Github Actions Workflow.
rename the Google-only accessible .clasp.json to other filename instead of default .clasp.json, while rename them back to .clasp.json before executing clasp push -f(link) inside your Github Action Workflow
Expected Behavior
People not work at Google can clone/commit this repo without overwriting this .clasp.json file.
Actual Behavior
Everyone outside Google needs to overwrite this .clasp.json file to run the clasp push to their GAS project.
Steps to Reproduce the Problem
login with personal gmail account
create a new Google Sheet and retrieve the GAS project ID through Extensions > Apps Script menu
Go to Project Settings to retrieve Script ID
Overwrite the scriptID within solutions/automations/mail-merge/.clasp.google-only.json
run clasp push under solutions/automations/mail-merge/ directory
But I have no idea how Googlers use these .clasp.json files, so feel free to provide any other idea, thanks!
Summary
The
.clasp.json
files contain the GAS project IDs only accessible inside Google. (example) However, people using clasp CLI to push to their GAS project ID will need to overwrite these files.What I think it might be better in either way:
add .clasp.json in .gitignore file but it will not work since this file is required for your Github Actions Workflow..clasp.json
to other filename instead of default.clasp.json
, while rename them back to.clasp.json
before executingclasp push -f
(link) inside your Github Action WorkflowExpected Behavior
People not work at Google can clone/commit this repo without overwriting this .clasp.json file.
Actual Behavior
Everyone outside Google needs to overwrite this .clasp.json file to run the
clasp push
to their GAS project.Steps to Reproduce the Problem
scriptID
within solutions/automations/mail-merge/.clasp.google-only.jsonclasp push
under solutions/automations/mail-merge/ directoryBut I have no idea how Googlers use these .clasp.json files, so feel free to provide any other idea, thanks!