Update README.md

[GrantBirki]

.noop

[GrantBirki]

.wcid

[github-actions[bot]]

Deployment Triggered 🚀

GrantBirki, started a noop deployment to production

You can watch the progress here 🔗

Branch: GrantBirki-patch-1

[github-actions[bot]]

Deployment Results :rocket:

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 GrantBirki-patch-1 to the production environment. This deployment was a success :rocket:.

This was a noop deployment.

[github-actions[bot]]

Lock Details 🔒

No active production deployment locks found for the GrantBirki/actions-sandbox repository

If you need to create a production lock, please comment .lock production

[GrantBirki]

.lock

[github-actions[bot]]

🔒 Deployment Lock Claimed

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

[GrantBirki]

.wcid

[GrantBirki]

.deploy

[github-actions[bot]]

Lock Details 🔒

The deployment lock is currently claimed by GrantBirki

• Reason: null
• Branch: GrantBirki-patch-1
• Created At: 2023-09-01T22:22:57.470Z
• Created By: GrantBirki
• Sticky: true
• Environment: production
• Comment Link: click here
• Lock Link: click here

The current lock has been active for 0d:0h:0m:42s

If you need to release the lock, please comment .unlock production

[github-actions[bot]]

Deployment Triggered 🚀

GrantBirki, started a branch deployment to production

You can watch the progress here 🔗

Branch: GrantBirki-patch-1

[github-actions[bot]]

Deployment Results :rocket:

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 GrantBirki-patch-1 to the production environment. This deployment was a success :rocket:.

[GrantBirki]

.lock --global

[github-actions[bot]]

🔒 Deployment Lock Claimed

This is a global deploy lock - All environments are now locked

You are now the only user that can trigger deployments globally until the deployment lock is removed

This lock is sticky and will persist until someone runs .unlock --global

[GrantBirki]

.deploy

[github-actions[bot]]

Deployment Triggered 🚀

GrantBirki, started a branch deployment to production

You can watch the progress here 🔗

Branch: GrantBirki-patch-1

[github-actions[bot]]

Deployment Results :rocket:

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 GrantBirki-patch-1 to the production environment. This deployment was a success :rocket:.