Chat command: deploy branch to env
Description
We already support deploying whatever is running in one environment, to another environment. But sometimes you just want to deploy whatever is in a branch. e.g. deploy master to production
without regard for whether master is deployed elsewhere. Specifically, this comes up with the I2P demo where we removed the staging stage in the demo and want to deploy directly to production after a merge.
Proposal
- Add chat command:
deploy <branch> to <env>
which would find the pipeline for HEAD of and look for a manual action that deploys to ; run it. If there is no pipeline for HEAD, or the manual action is blocked, we should either fail right away, or wait for the action to be available. The latter is probably much harder to implement.
Links / references
Documentation blurb
(Write the start of the documentation of this feature here, include:
- Why should someone use it; what's the underlying problem.
- What is the solution.
- How does someone use this
During implementation, this can then be copied and used as a starter for the documentation.)
Edited by Jason Yavorska