docs: add projectId to clasp configuration examples#19
Merged
Conversation
All setup docs now include the optional projectId field in .clasp.json examples and CI/CD variable tables. This makes the GCP project association declarative per script, supporting organizations that distribute scripts across multiple GCP projects.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.clasp.jsonの設定例にprojectIdフィールドを追加（GitHub / GitLab の全 setup docs）CLASP_JSON値にもprojectIdを反映projectIdの意味と確認方法を説明する注釈を追加（en/ja 両方）スクリプトが複数の GCP プロジェクトに分散する組織向けに、紐づけを宣言的に管理できるようにする。
projectIdは省略可能なので既存ユーザーへの影響はない。Test plan
pnpm run checkが通ること