Closed GrantBirki closed 2 months ago
REVIEW_REQUIRED
FAILURE
This is usually caused by missing PR approvals or CI checks failing
.wcid
No active production
deployment locks found for the GrantBirki/actions-sandbox
repository
If you need to create a
production
lock, please comment.lock production
.lock --reason because i said so
You are now the only user that can trigger deployments to the production
environment until the deployment lock is removed
This lock is sticky and will persist until someone runs
.unlock production
.wcid
The deployment lock is currently claimed by GrantBirki
because i said so
test
2024-07-06T17:34:22.949Z
GrantBirki
true
production
The current lock has been active for 0d:0h:0m:20s
If you need to release the lock, please comment
.unlock production
.wcid --global
.unlock --global
No active global
deployment locks found for the GrantBirki/actions-sandbox
repository
If you need to create a
global
lock, please comment.lock --global
🔓 There is currently no global
deployment lock set
.unlock production
The production
deployment lock has been successfully removed
.noop to production
GrantBirki, started a noop deployment to production
You can watch the progress here 🔗
noop:
test
The following variables are available to use in this template:
environment
- The name of the environment (String)environment_url
- The URL of the environment (String) {Optional}status
- The status of the deployment (String) - success
, failure
, or unknown
noop
- Whether or not the deployment is a noop (Boolean)ref
- The ref of the deployment (String)actor
- The GitHub username of the actor who triggered the deployment (String)Here is an example:
GrantBirki deployed branch test
to the production environment. This deployment was a success :rocket:.
This was a noop deployment.
Please make sure to get a review on this pull request as you currently have none
.deploy
GrantBirki, started a branch deployment to production
You can watch the progress here 🔗
Branch:
test
The following variables are available to use in this template:
environment
- The name of the environment (String)environment_url
- The URL of the environment (String) {Optional}status
- The status of the deployment (String) - success
, failure
, or unknown
noop
- Whether or not the deployment is a noop (Boolean)ref
- The ref of the deployment (String)actor
- The GitHub username of the actor who triggered the deployment (String)Here is an example:
GrantBirki deployed branch test
to the production environment. This deployment was a success :rocket:.
.deploy 61034499d3a7a1991d8b30da47d8f601280be1ec
false
sha deployments have not been enabled
.deploy 61034499d3a7a1991d8b30da47d8f601280be1ec
GrantBirki, started a sha deployment to production
You can watch the progress here 🔗
sha:
61034499d3a7a1991d8b30da47d8f601280be1ec
The following variables are available to use in this template:
environment
- The name of the environment (String)environment_url
- The URL of the environment (String) {Optional}status
- The status of the deployment (String) - success
, failure
, or unknown
noop
- Whether or not the deployment is a noop (Boolean)ref
- The ref of the deployment (String)actor
- The GitHub username of the actor who triggered the deployment (String)Here is an example:
GrantBirki deployed branch 61034499d3a7a1991d8b30da47d8f601280be1ec
to the production environment. This deployment was a success :rocket:.
.deploy
Your branch is behind the base branch and will need to be updated before deployments can continue.
BEHIND
warn
Please ensure your branch is up to date with the
main
branch and try again
.deploy
BEHIND
force
I went ahead and updated your branch with
main
- Please try again once this operation is complete
.deploy