-
Notifications
You must be signed in to change notification settings - Fork 45
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 to deploy 'draft' PRs to some environments #163
Comments
👋 Great question @szymonpk! I'll weigh in my own thoughts / opinions here. Professionally and in personal projects, I have never deployed a pull request that was in a That being said, there are a lot of ways to embark in the journey on software development and different ways for folks to use GitHub to accomplish what they need to do. One of the core concepts of the I personally would suggest to steer away from making I will take a look at the code in this project and see what adjustments, and input options need to be added to enable your team to do this. Thanks! |
We treat some environments very 'lightly' ;-) In our case, deployment may be the easiest way to present current work (in progress) to a wider audience. Sometimes we work on rather complex data sets. Also, if this action gets approval in our org, we probably would like to use it for 'dynamic environments' at some point (created per PR). In such case, a draft-blocker would be an issue :( As for the implementation (I am not proficient in any form of JS), I was thinking it could be done like |
@szymonpk I'll try and accomplish this soon for ya! |
Details
I am wondering. Would it be a good idea to have a list of environments that we can deploy to even if PR is in a draft state?
In "my" organization, people can deploy to some stages before the review. Marking PR as "ready" triggers review requests, and it may be unwanted in most cases.
The text was updated successfully, but these errors were encountered: