-
Notifications
You must be signed in to change notification settings - Fork 5
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
Allow calling even if deployment exists #3
Comments
Hey @kzlar apologies for the delay here! Appreciate the kind words. So I have the same setup with neondb but not exactly sure how calling even if deployment exists "fixes" this or what it addresses Currently my setup using this action with neondb is as follows:
As this action only deals with railway and doesn't affect neon (or any database for that matter). |
Does this help @kzlar ? It doesn't necessarily need to use "opened" just had that as an example on the README. The railway action can be different than the condition for the db. |
@Faolain Hey - I replied on the PR #5 (comment) let me know if it makes things clearer. |
Hi @Faolain !
First of all, really appreciate your effort on this! It just works and saved me hours of figuring this out myself!
I wanted to ask whether it would be possible to make this action work without
if: github.event.action == 'opened'
. I'm using the railway deployment in conjunction with neondb branch create (neondatabase/create-branch-action@v5
) and neondb's action is called every time and silently exists if the branch already exists. I think that would be a great addition to this action as well.Thank you for your consideration!
The text was updated successfully, but these errors were encountered: