Skip to content

Comments

chore: update env variables for atoms e2e yml#23883

Merged
Ryukemeister merged 2 commits intomainfrom
update-workflows-for-examples-e2e
Sep 17, 2025
Merged

chore: update env variables for atoms e2e yml#23883
Ryukemeister merged 2 commits intomainfrom
update-workflows-for-examples-e2e

Conversation

@Ryukemeister
Copy link
Contributor

No description provided.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 17, 2025

Walkthrough

The PR modifies .github/workflows/e2e-atoms.yml by adding two environment variables in the workflow’s env block: ATOMS_E2E_APPLE_ID and ATOMS_E2E_APPLE_CONNECT_APP_SPECIFIC_PASSCODE. Each variable references a corresponding GitHub Actions secret with the same name (secrets.ATOMS_E2E_APPLE_ID and secrets.ATOMS_E2E_APPLE_CONNECT_APP_SPECIFIC_PASSCODE). No other workflow steps, jobs, or configurations are changed.

Possibly related PRs

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Description Check ❓ Inconclusive No pull request description was provided by the author, so there is no description content to evaluate against the changeset; this absence makes the check inconclusive because we cannot determine whether an author-provided description would be related or useful. Please add a brief PR description summarizing the change (for example: "Add ATOMS_E2E_APPLE_ID and ATOMS_E2E_APPLE_CONNECT_APP_SPECIFIC_PASSCODE environment variables to .github/workflows/e2e-atoms.yml") and include any reason or testing notes so reviewers can quickly understand the intent.
✅ Passed checks (2 passed)
Check name Status Explanation
Title Check ✅ Passed The title "chore: update env variables for atoms e2e yml" concisely and accurately summarizes the primary change: updates to environment variables in the atoms e2e GitHub Actions workflow (the changeset adds two secrets to the env block). It is short, specific to the affected workflow file, and free of extraneous noise.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch update-workflows-for-examples-e2e

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


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

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

@Ryukemeister Ryukemeister enabled auto-merge (squash) September 17, 2025 07:24
@keithwillcode keithwillcode added core area: core, team members only platform Anything related to our platform plan labels Sep 17, 2025
@graphite-app graphite-app bot requested a review from a team September 17, 2025 07:24
@dosubot dosubot bot added the ❗️ .env changes contains changes to env variables label Sep 17, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.github/workflows/e2e-atoms.yml (2)

16-17: Scope secrets to only the step that needs them to reduce exposure.

Top-level env exposes these secrets to every step, including third‑party actions. Prefer step‑level env for “Run E2E Atoms Tests”.

 env:
   NODE_OPTIONS: --max-old-space-size=8096
   ATOMS_E2E_OAUTH_CLIENT_ID: ${{ secrets.ATOMS_E2E_OAUTH_CLIENT_ID }}
   ATOMS_E2E_OAUTH_CLIENT_SECRET: ${{ secrets.ATOMS_E2E_OAUTH_CLIENT_SECRET }}
   ATOMS_E2E_API_URL: ${{ secrets.ATOMS_E2E_API_URL }}
   ATOMS_E2E_ORG_ID: ${{ secrets.ATOMS_E2E_ORG_ID }}
   ATOMS_E2E_OAUTH_CLIENT_ID_BOOKER_EMBED: ${{ secrets.ATOMS_E2E_OAUTH_CLIENT_ID_BOOKER_EMBED }}
-  ATOMS_E2E_APPLE_ID: ${{ secrets.ATOMS_E2E_APPLE_ID }}
-  ATOMS_E2E_APPLE_CONNECT_APP_SPECIFIC_PASSCODE: ${{ secrets.ATOMS_E2E_APPLE_CONNECT_APP_SPECIFIC_PASSCODE }}
   DATABASE_DIRECT_URL: ${{ secrets.CI_DATABASE_URL }}
   DATABASE_URL: ${{ secrets.CI_DATABASE_URL }}
@@
       - name: Run E2E Atoms Tests
         working-directory: packages/platform/examples/base
+        env:
+          ATOMS_E2E_APPLE_ID: ${{ secrets.ATOMS_E2E_APPLE_ID }}
+          ATOMS_E2E_APPLE_CONNECT_APP_SPECIFIC_PASSCODE: ${{ secrets.ATOMS_E2E_APPLE_CONNECT_APP_SPECIFIC_PASSCODE }}
         run: yarn test:e2e

16-17: Terminology nit: consider APP_STORE_CONNECT in the name.

Apple’s product is “App Store Connect”; APPLE_CONNECT may confuse future readers.

If renaming is feasible without breaking callers/secrets, prefer:

  • ATOMS_E2E_APP_STORE_CONNECT_APP_SPECIFIC_PASSWORD
  • Keep current as an alias during migration if needed.
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between fd87954 and 848dd60.

📒 Files selected for processing (1)
  • .github/workflows/e2e-atoms.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)
  • GitHub Check: Install dependencies / Yarn install & cache
  • GitHub Check: Install dependencies / Yarn install & cache
  • GitHub Check: Install dependencies / Yarn install & cache
  • GitHub Check: Install dependencies / Yarn install & cache
  • GitHub Check: Install dependencies / Yarn install & cache
  • GitHub Check: Install dependencies / Yarn install & cache
  • GitHub Check: Install dependencies / Yarn install & cache
  • GitHub Check: Install dependencies / Yarn install & cache
  • GitHub Check: Install dependencies / Yarn install & cache
  • GitHub Check: Install dependencies / Yarn install & cache
🔇 Additional comments (1)
.github/workflows/e2e-atoms.yml (1)

16-17: Make secrets available to this reusable workflow (declare or ensure callers pass them).

Because this workflow is invoked via workflow_call, ${{ secrets.* }} will be empty unless the reusable workflow declares the secrets under workflow_call: secrets: or every caller passes them (or uses secrets: inherit). If not wired, jobs will run with empty env vars and tests may fail.

Two options:

  • Declare required secrets here (preferred) — add:
 on:
-  workflow_call:
+  workflow_call:
+    secrets:
+      ATOMS_E2E_APPLE_ID:
+        required: true
+      ATOMS_E2E_APPLE_CONNECT_APP_SPECIFIC_PASSCODE:
+        required: true
  • Or confirm each caller uses secrets: inherit or maps these secrets when calling.

To locate callers, run:

grep -RIn --include="*.yml" --include="*.yaml" "e2e-atoms.yml" .github/workflows || echo "No callers found"

@vercel
Copy link

vercel bot commented Sep 17, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
cal Ignored Ignored Sep 17, 2025 7:48am
cal-eu Ignored Ignored Sep 17, 2025 7:48am

@github-actions
Copy link
Contributor

E2E results are ready!

@Ryukemeister Ryukemeister merged commit f9095d2 into main Sep 17, 2025
64 of 66 checks passed
@Ryukemeister Ryukemeister deleted the update-workflows-for-examples-e2e branch September 17, 2025 08:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core area: core, team members only ❗️ .env changes contains changes to env variables platform Anything related to our platform plan ready-for-e2e size/XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants