Closed GrantBirki closed 4 months ago
.wcid 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
No active production
deployment locks found for the GrantBirki/actions-sandbox
repository
If you need to create a
production
lock, please comment.lock production
.deploy to production
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:.
.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
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
.noop