Skip to content

chore(ci): Use repo variables for non-sensitive config#21037

Open
neo-jesse wants to merge 10 commits intoedgefrom
feature/replace-secrets-with-variables
Open

chore(ci): Use repo variables for non-sensitive config#21037
neo-jesse wants to merge 10 commits intoedgefrom
feature/replace-secrets-with-variables

Conversation

@neo-jesse
Copy link
Copy Markdown
Collaborator

chore(ci): Use repo variables for non-sensitive config

Summary:

  • Use GitHub Actions variables instead of secrets for: SENTRY_ORG, SENTRY_PROJECT, MIXPANEL_INGEST_USER, OT_APP_APPLE_ID_V2.
  • Updated workflows: pd-test-build-deploy.yaml, app-test-build-deploy.yaml, odd-memory-usage-test.yaml.
  • These values are not highly sensitive; variables allow default values and clearer visibility in the UI. Add the same names under Settings → Actions → Variables and remove the corresponding secrets once variables are in place.

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.56%. Comparing base (98e7813) to head (73a87f2).
⚠️ Report is 44 commits behind head on edge.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             edge   #21037      +/-   ##
==========================================
- Coverage   57.20%   56.56%   -0.65%     
==========================================
  Files        3987     4026      +39     
  Lines      326739   333752    +7013     
  Branches    46475    47262     +787     
==========================================
+ Hits       186908   188776    +1868     
- Misses     139612   144747    +5135     
- Partials      219      229      +10     
Flag Coverage Δ
app 45.16% <ø> (+0.22%) ⬆️
protocol-designer 19.94% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 394 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@neo-jesse neo-jesse marked this pull request as ready for review March 16, 2026 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant