chore: use sample env files for tests#981
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Actions CI workflow to avoid relying on repository secrets by preparing .env files from sample env templates so forked PRs can run tests.
Changes:
- Adds a workflow step intended to create
.envand.env.testfrom sample env files. - Removes the job-level
env:secret-based configuration from Postgres and OrioleDB test jobs.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This comment has been minimized.
This comment has been minimized.
Pull Request Test Coverage Report for Build 24036022900Details
💛 - Coveralls |
Signed-off-by: ferhat elmas <elmas.ferhat@gmail.com>
fenos
approved these changes
Apr 7, 2026
fenos
approved these changes
Apr 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Chore
What is the current behavior?
External PRs fail running tests since they can't get the secrets.
What is the new behavior?
Use sample env files to run tests.
Additional context
It should help increasing contribution convenience.