Skip to content

ci(e2e): enable Google Calendar E2E suites in workflow #293

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
h4yfans merged 1 commit into from
Apr 20, 2026
Merged

ci(e2e): enable Google Calendar E2E suites in workflow #293

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .github/workflows/e2e.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,15 @@ jobs:
run: pnpm build

- name: Run Electron E2E tests (shard ${{ matrix.shard }})
env:
# Google Calendar E2E credentials — gated on the secrets being
# configured at the repo level. Empty strings when unset cause the
# Calendar suites' `CREDS_PRESENT` check to fail and the tests skip
# cleanly, so forks without access still pass CI.
GOOGLE_CALENDAR_E2E: '1'
GOOGLE_CALENDAR_E2E_REFRESH_TOKEN: ${{ secrets.GOOGLE_CALENDAR_E2E_REFRESH_TOKEN }}
GOOGLE_CALENDAR_E2E_CLIENT_ID: ${{ secrets.GOOGLE_CALENDAR_E2E_CLIENT_ID }}
GOOGLE_CALENDAR_E2E_CLIENT_SECRET: ${{ secrets.GOOGLE_CALENDAR_E2E_CLIENT_SECRET }}
run: |
# keytar -> libsecret needs an active dbus session + an unlocked
# gnome-keyring with the default "login" collection present.
Expand Down
Loading