Skip to content

will the integration tests run at home question mark#7705

Draft
n1ru4l wants to merge 3 commits intosupertokens-core-at-homefrom
will-the-integration-tests-run-at-home-question-mark
Draft

will the integration tests run at home question mark#7705
n1ru4l wants to merge 3 commits intosupertokens-core-at-homefrom
will-the-integration-tests-run-at-home-question-mark

Conversation

@n1ru4l
Copy link
Contributor

@n1ru4l n1ru4l commented Feb 18, 2026

No description provided.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @n1ru4l, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on refining the integration test environment by correctly configuring the SuperTokens authentication service. The changes involve enabling a specific 'home' mode for SuperTokens and supplying essential token keys, which are critical for the authentication and authorization processes during automated test execution. This ensures that integration tests can run reliably and securely.

Highlights

  • SuperTokens Configuration: Configured SuperTokens environment variables to ensure proper functionality within the integration testing setup.
  • Integration Test Environment: Enabled the SUPERTOKENS_AT_HOME flag, indicating a specific mode for SuperTokens operation in the integration test environment.
  • Authentication Keys: Provided the necessary SUPERTOKENS_REFRESH_TOKEN_KEY and SUPERTOKENS_ACCESS_TOKEN_KEY to the graphql-engine service for secure token handling during tests.
Changelog
  • integration-tests/.env
    • Updated the SUPERTOKENS_AT_HOME environment variable from 0 to 1.
  • integration-tests/docker-compose.integration.yaml
    • Added SUPERTOKENS_AT_HOME with a value of 1 to the graphql-engine service environment.
    • Included SUPERTOKENS_REFRESH_TOKEN and SUPERTOKENS_ACCESS_TOKEN_KEY environment variables for the graphql-engine service.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 18, 2026

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package Version Info
@graphql-hive/cli 0.58.1-alpha-20260219005536-c56e7bdde716bd43b92cc3583e50c0571fbd9589 npm ↗︎ unpkg ↗︎
hive 9.5.0-alpha-20260219005536-c56e7bdde716bd43b92cc3583e50c0571fbd9589 npm ↗︎ unpkg ↗︎

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request enables the supertokens-at-home feature for integration tests by setting the SUPERTOKENS_AT_HOME environment variable to 1 and adding the required token keys to the docker-compose.integration.yaml configuration. My review identifies a likely typo in an environment variable name which could cause issues.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 18, 2026

🐋 This PR was built and pushed to the following Docker images:

Targets: build

Platforms: linux/amd64

Image Tag: c56e7bdde716bd43b92cc3583e50c0571fbd9589

@github-actions
Copy link
Contributor

github-actions bot commented Feb 18, 2026

💻 Website Preview

The latest changes are available as preview in: https://pr-7705.hive-landing-page.pages.dev

@n1ru4l n1ru4l force-pushed the will-the-integration-tests-run-at-home-question-mark branch from 50a4a9d to 25a1f74 Compare February 18, 2026 15:16
@n1ru4l n1ru4l force-pushed the supertokens-core-at-home branch from 6a7d504 to b8d9dcb Compare February 18, 2026 15:17
@n1ru4l n1ru4l force-pushed the will-the-integration-tests-run-at-home-question-mark branch from 25a1f74 to dbe58c2 Compare February 18, 2026 15:17
@n1ru4l n1ru4l force-pushed the will-the-integration-tests-run-at-home-question-mark branch from dbe58c2 to f3eb62e Compare February 18, 2026 18:07
@n1ru4l n1ru4l force-pushed the will-the-integration-tests-run-at-home-question-mark branch from f3eb62e to f22dead Compare February 18, 2026 18:17
@n1ru4l n1ru4l force-pushed the will-the-integration-tests-run-at-home-question-mark branch from f22dead to a26f083 Compare February 18, 2026 19:07
@n1ru4l n1ru4l force-pushed the will-the-integration-tests-run-at-home-question-mark branch from a26f083 to b5f6a4b Compare February 18, 2026 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments