Closed GrantBirki closed 1 year ago
.deploy development
.deploy
.deploy potato
GrantBirki, started a branch deployment to staging
You can watch the progress here 🔗
Branch:
test
GrantBirki, started a branch deployment to production
You can watch the progress here 🔗
Branch:
test
GrantBirki successfully deployed branch test
to staging
GrantBirki, started a branch deployment to development
You can watch the progress here 🔗
Branch:
test
GrantBirki successfully deployed branch test
to production
No matching environment target found. Please check your command and try again. You can read more about environment targets in the README of this Action.
The following environment targets are available:
production,development,staging
GrantBirki successfully deployed branch test
to development
.lock --reason small change to mappings for risk rating
No matching environment target found. Please check your command and try again. You can read more about environment targets in the README of this Action.
The following environment targets are available:
production,sandbox
.lock --reason small change to mappings for risk rating
No matching environment target found. Please check your command and try again. You can read more about environment targets in the README of this Action.
The following environment targets are available:
production,sandbox
No matching environment target found. Please check your command and try again. You can read more about environment targets in the README of this Action.
The following environment targets are available:
production,sandbox
.lock --reason small change to mappings for risk rating
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
.unlock --reason even though I don't need one
🔓 There is currently no --reason even though I don't need one
deployment lock set
.lock production --reason "here is a reason with some quotes"
GrantBirki, you are already the owner of the current production
environment deployment lock
The current lock has been active for 0d:0h:0m:49s
If you need to release the lock, please comment
.unlock production
.unlock
The production
deployment lock has been successfully removed
.lock --reason "here is a reason with ' some weird' quotes"
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
"here is a reason with ' some weird' quotes"
test
2023-03-16T21:07:09.981Z
GrantBirki
true
production
The current lock has been active for 0d:0h:0m:35s
If you need to release the lock, please comment
.unlock production
.unlock
The production
deployment lock has been successfully removed
.deploy staging