This repository was archived by the owner on Feb 11, 2026. It is now read-only.
Repository navigation
implement cicd - #18
Merged
Merged
Conversation
…BASE_URL and add env variable in CI/CD workflow
There was a problem hiding this comment.
Pull request overview
This pull request modifies the handling of the DATABASE_URL environment variable for Prisma configuration. While the PR title suggests implementing new CI/CD infrastructure, the changes actually enhance existing CI/CD workflows by adding explicit DATABASE_URL environment variable configuration. The modifications aim to ensure Prisma commands have valid database URLs during both CI/CD execution and local development by introducing fallback values.
Key changes include:
- Replacing the
env()helper with directprocess.env.DATABASE_URLaccess and a fallback connection string inprisma.config.ts - Adding explicit DATABASE_URL environment variables to Prisma Generate steps in the CI/CD workflow
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| prisma.config.ts | Removes the env helper dependency and adds a fallback PostgreSQL connection string for DATABASE_URL |
| .github/workflows/cicd.yml | Explicitly sets DATABASE_URL environment variable for Prisma Generate steps in both build_test and prisma_migrate jobs |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Add DATABASE_URL env var to Prisma generate steps in workflow - Update prisma.config.ts to use process.env with fallback - Add test:ci script to package.json - Fix Jest configuration to support @/* path aliases - Update tests to properly mock dependencies - Remove obsolete app.controller.spec.ts test
…t location in Dockerfile
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This pull request updates how the
DATABASE_URLenvironment variable is handled for Prisma in both the GitHub Actions workflow and the Prisma configuration. The main goal is to ensure that a default database URL is available if the environment variable is not set, improving reliability in different environments.Prisma configuration improvements:
prisma.config.tsto useprocess.env.DATABASE_URLdirectly, with a fallback to a default PostgreSQL connection string if the environment variable is not set. This removes reliance on the customenvhelper and ensures Prisma always has a valid database URL. [1] [2]CI/CD workflow adjustments:
.github/workflows/cicd.ymlfile, explicitly sets theDATABASE_URLenvironment variable for the "Prisma Generate" step in both jobs, using a hardcoded value for local runs and a secret for production/deployment runs. This ensures Prisma commands have the necessary configuration during CI/CD. [1] [2]…BASE_URL and add env variable in CI/CD workflow