Update and rename docs/2. Pre Onboarding/04. GCS Setup/03. Create an …

[SangeetaMishr]

…account in Google Cloud Storage GCS.md to docs/2. Pre Onboarding/01.Google Cloud Storage (GCS) Setup.md

Summary by CodeRabbit

• Documentation
  • Added a detailed GCS setup guide with optional UPI-based signup steps, including images.
  • Clarified guidance on public vs. private GCS buckets, with cautions for sensitive data.
  • Introduced a section on assigning access to a service account, with step-by-step instructions and visuals.
  • Reorganized integration headings for GCS, BigQuery API, and Google Sheets API for consistency.
  • Expanded reference links, including pricing and Google Help resources.
  • Rewrote introductory context, replacing the prior “Why is the setup needed?” subsection.

[coderabbitai]

Walkthrough

Documentation updates to the GCS setup guide: removed a rationale subsection, added a detailed UPI-based GCS signup flow, adjusted heading levels, added guidance on public vs private buckets, introduced service account access assignment steps, and expanded reference links. No code changes.

Changes

Cohort / File(s)	Summary of Changes
GCS Setup Docs Refresh docs/2. Pre Onboarding/01.Google Cloud Storage (GCS) Setup.md	Rewrote intro; added step-by-step “GCS Setup with UPI” with images; clarified public vs private bucket guidance; added “Assign access to the Service Account in Google Console” with screenshots; demoted some headings (## → ###) for GCS/BigQuery/Sheets integration sections; expanded references.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Create GCS_Bucket.md #343 — Adds/expands guidance on when to use public vs private GCS buckets, overlapping with this PR’s new bucket access recommendations.

Suggested reviewers

• shijithkjayan
• Fawas003

Poem

I hop through docs with tidy feet,
New steps for GCS—so neat!
UPI trails and buckets bright,
Public, private—choose your light.
Service accounts now aligned,
Carrots checked, permissions signed.
Thump-thump—onward, well-defined! 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title refers to updating and renaming the documentation file and mentions the file path, which matches a real aspect of the changeset but does not concisely capture the main content revisions. It's overly focused on file location rather than summarizing the substantive update to the GCS setup instructions.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch Google-Cloud-Storage.md

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 594f6c1 and ea41cd0.

📒 Files selected for processing (1)

• docs/2. Pre Onboarding/01.Google Cloud Storage (GCS) Setup.md (4 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🚀 Deployed on https://deploy-preview-446--glific-docs.netlify.app