Skip to content
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.

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

src/input: support setting the config file path from the action #59

Merged
merged 3 commits into from
Aug 12, 2023

Conversation

rotemtam
Copy link
Member

Closes #58

@github-actions
Copy link

Atlas Lint Report

Analyzed migrations2

StatusStepResultDiagnostics
Detect New Migration FilesFound 0 new migration files (from 0 total)
Replay Migration FilesLoaded 0 changes on dev database
Connect your project to Atlas Cloud to get more safety checks

Migrations automatically reviewed by Atlas

@github-actions
Copy link

Atlas Lint Report

Analyzed migrations

StatusStepResultDiagnostics
Detect New Migration FilesFound 0 new migration files (from 0 total)
Replay Migration FilesLoaded 0 changes on dev database
Connect your project to Atlas Cloud to get more safety checks

Migrations automatically reviewed by Atlas

@rotemtam rotemtam requested review from a8m, giautm and a team August 12, 2023 06:26
@@ -78,6 +78,11 @@ jobs:

Configure the action by passing input parameters in the `with:` block.

#### `config-path`
Copy link
Member

Choose a reason for hiding this comment

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

👍

Maybe deprecate project-env and rename it to config-env?

@rotemtam rotemtam merged commit 0175440 into master Aug 12, 2023
3 checks passed
@dorav dorav deleted the config branch November 2, 2023 11:26
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.

How to fail the GHA workflow if backwards incompatible changes detected?
2 participants