test

[github-actions[bot]]

Deployment Triggered 🚀

GrantBirki, started a sha deployment to production

You can watch the progress here 🔗

sha: test

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

[GrantBirki]

.deploy production

[github-actions[bot]]

Deployment Triggered 🚀

GrantBirki, started a sha deployment to production

You can watch the progress here 🔗

sha: test

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

[GrantBirki]

.deploy to production

[github-actions[bot]]

Deployment Triggered 🚀

GrantBirki, started a sha deployment to production

You can watch the progress here 🔗

sha: test

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

[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]

.unlock

[github-actions[bot]]

🔓 Deployment Lock Removed

The production deployment lock has been successfully removed

[GrantBirki]

.deploy

[GrantBirki]

.deploy

[github-actions[bot]]

Missing Explicit Environment

This style of command is known as a "naked command" and is not allowed based on your configuration. "Naked commands" are commands that do not explicitly specify an environment, for example .deploy would be a "naked command" whereas .deploy production would not be.

View the documentation to learn more

[GrantBirki]

.deploy

[github-actions[bot]]

Missing Explicit Environment

Suggestion

.deploy <environment>

Explanation

This style of command is known as a "naked command" and is not allowed based on your configuration. "Naked commands" are commands that do not explicitly specify an environment, for example .deploy would be a "naked command" whereas .deploy <environment> would not be.

View the documentation to learn more

[GrantBirki]

.lock --reason testing things out

[github-actions[bot]]

Missing Explicit Environment

Suggestion

.lock <environment>

Explanation

This style of command is known as a "naked command" and is not allowed based on your configuration. "Naked commands" are commands that do not explicitly specify an environment, for example .lock would be a "naked command" whereas .lock <environment> would not be.

View the documentation to learn more

[GrantBirki]

.unlock

[github-actions[bot]]

Missing Explicit Environment

Suggestion

.unlock <environment>

Explanation

This style of command is known as a "naked command" and is not allowed based on your configuration. "Naked commands" are commands that do not explicitly specify an environment, for example .unlock would be a "naked command" whereas .unlock <environment> would not be.

View the documentation to learn more

[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]

.unlock --global

[github-actions[bot]]

🔓 Deployment Lock Removed

The global deployment lock has been successfully removed

[GrantBirki]

.wcid

[GrantBirki]

.wcid production

[GrantBirki]

.deploy production

[github-actions[bot]]

Missing Explicit Environment

Suggestion

.wcid <environment>

Explanation

This style of command is known as a "naked command" and is not allowed based on your configuration. "Naked commands" are commands that do not explicitly specify an environment, for example .wcid would be a "naked command" whereas .wcid <environment> would not be.

View the documentation to learn more

[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

[github-actions[bot]]

Deployment Triggered 🚀

GrantBirki, started a sha deployment to production

You can watch the progress here 🔗

sha: test

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

[GrantBirki]

.deploy to production

[github-actions[bot]]

Deployment Triggered 🚀

GrantBirki, started a sha deployment to production

You can watch the progress here 🔗

sha: test

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

[GrantBirki]

.deploy to blah

[github-actions[bot]]

⚠️ Cannot proceed with deployment

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]

.deploy production

[github-actions[bot]]

Deployment Triggered 🚀

GrantBirki, started a sha deployment to production

You can watch the progress here 🔗

sha: test

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

[github-actions[bot]]

Deployment Triggered 🚀

GrantBirki, started a sha deployment to production

You can watch the progress here 🔗

sha: test

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

[github-actions[bot]]

Deployment Triggered 🚀

GrantBirki, started a sha deployment to production

You can watch the progress here 🔗

sha: test

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

[GrantBirki]

.deploy production

[github-actions[bot]]

Deployment Triggered 🚀

GrantBirki, started a branch deployment to production

You can watch the progress here 🔗

Branch: test

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

[GrantBirki]

.lock

[github-actions[bot]]

Missing Explicit Environment

Suggestion

.lock <environment>

Explanation

This style of command is known as a "naked command" and is not allowed based on your configuration. "Naked commands" are commands that do not explicitly specify an environment, for example .lock would be a "naked command" whereas .lock <environment> would not be.

View the documentation to learn more

[GrantBirki]

.lock production