Skip to content

fix(ci): skip E2E tests when REPO_GEMINI_API_KEY is not set#972

Open
gspencergoog wants to merge 1 commit into
flutter:mainfrom
gspencergoog:fix-ci-e2e
Open

fix(ci): skip E2E tests when REPO_GEMINI_API_KEY is not set#972
gspencergoog wants to merge 1 commit into
flutter:mainfrom
gspencergoog:fix-ci-e2e

Conversation

@gspencergoog

@gspencergoog gspencergoog commented Jun 15, 2026

Copy link
Copy Markdown
Collaborator

Summary

Only run the E2E test job in the eval workflow if the REPO_GEMINI_API_KEY secret is not empty. This avoids workflow failures on branch pushes from Dependabot, which does not have access to repository secrets.

Changes

  • Modified the eval-job conditional in .github/workflows/e2e.yaml to include secrets.REPO_GEMINI_API_KEY != ''.

Impact & risks

There are no risks. On Dependabot runs, the E2E job will be skipped, which satisfies required status checks. It will continue to run as expected on collaborator pushes and scheduled runs.

Testing

  • Checked that the conditional syntax is valid.

@github-actions

Copy link
Copy Markdown

Package publishing

Package Version Status Publish tag (post-merge)
package:a2ui_core 0.0.1-wip002 ready to publish a2ui_core-v0.0.1-wip002
package:genai_primitives 0.2.4 ready to publish genai_primitives-v0.2.4
package:genui 0.9.2 already published at pub.dev
package:genui_a2a 0.9.0 already published at pub.dev
package:json_schema_builder 0.1.5 already published at pub.dev

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

@gspencergoog gspencergoog requested a review from polina-c June 15, 2026 23:56
# Do not run on forked branches,
# because the test does not have access to secrets in forks.
if: github.repository == 'flutter/genui'
if: github.repository == 'flutter/genui' && secrets.REPO_GEMINI_API_KEY != ''

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

How about leaving just second condition so that forks can have key configured and test running?

@polina-c polina-c left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM with one comment

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.

2 participants