Skip to content

How to auto-deploy an environment #381

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

Closed
adajou opened this issue Mar 26, 2025 · 2 comments
Closed

How to auto-deploy an environment #381

adajou opened this issue Mar 26, 2025 · 2 comments
Labels
question Further information is requested or the issue is a question

Comments

@adajou
Copy link

adajou commented Mar 26, 2025

Details

Is there a possibility to auto deploy an environment after CI and all the checks have passed? I have thought of a way of doing that: In my CI pipeline I create a .deploy dev comment in my pull request. The problem is that the github bot will not trigger a deployment so I need to create this comment as a user that is a collaborator in this same repository. I was thinking of using a github app (or a service account) just as described in issue #297. How shall I use this app as admins?

Is there any other way to autodeploy than my suggestion above?

@adajou adajou added the question Further information is requested or the issue is a question label Mar 26, 2025
@GrantBirki
Copy link
Member

👋 @adajou Auto-deploy isn't something I have personally ever used with this Action or heard of other people doing. That isn't to say it can't be done, just that I haven't seen it before.

There is an open pull request in a related project to this one to support the usage of GitHub Apps triggering these types of Actions -> github/command#70

However, none of that has landed yet.

The core design behind this Action is to really leave it up to the user how they go about their deployment process in their own unique way and prove best practices and guard rails to accomplish that. Commenting .deploy on a PR is generally something that a human does and maybe a different deployment approach suits your use case better.

@adajou
Copy link
Author

adajou commented Mar 27, 2025

Hi @GrantBirki thanks for the reply. I totally get it when it comes to the purpose of this action. The aim for us is to have the possibility to auto-build the dev environment and use manual commands for stage and prod and also we use the command action for own defined commands so semi-automated branch deployment is what we are trying to achieve

@adajou adajou closed this as completed Apr 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested or the issue is a question
Projects
None yet
Development

No branches or pull requests

2 participants