Closed GrantBirki closed 1 year ago
.noop
GrantBirki, started a noop deployment to production
You can watch the progress here 🔗
Branch:
branch-deploy-demo
GrantBirki successfully noop deployed branch branch-deploy-demo
to production
.deploy
GrantBirki, started a branch deployment to production
You can watch the progress here 🔗
Branch:
branch-deploy-demo
GrantBirki successfully deployed branch branch-deploy-demo
to production
.deploy to development
GrantBirki, started a branch deployment to development
You can watch the progress here 🔗
Branch:
branch-deploy-demo
GrantBirki successfully deployed branch branch-deploy-demo
to development
.lock production --reason I am testing a very risky change
GrantBirki, you are already the owner of the current production
environment deployment lock
The current lock has been active for 1d:7h:18m:20s
If you need to release the lock, please comment
.unlock production
.unlock production
The production
deployment lock has been successfully removed
.deploy main to production
GrantBirki, started a branch deployment to production
You can watch the progress here 🔗
Branch:
main
GrantBirki successfully deployed branch main
to production
.noop main to development
GrantBirki, started a noop deployment to development
You can watch the progress here 🔗
Branch:
main
GrantBirki successfully noop deployed branch main
to development
.lock --global --reason there are fires in all environments right now
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
.lock --info
The deployment lock is currently claimed by GrantBirki This is a global deploy lock - All environments are currently locked
there are fires in all environments right now
branch-deploy-demo
2023-07-19T22:24:33.052Z
GrantBirki
true
all
true
The current lock has been active for 0d:0h:0m:27s
If you need to release the lock, please comment
.unlock --global
.help
This help message was automatically generated based on the inputs provided to this Action.
.help
- Show this help message.deploy
- Deploy this branch to the production
environment.deploy main
- Rollback the production
environment to the main
branch.noop
- Deploy this branch to the production
environment in noop mode.lock
- Obtain the deployment lock (will persist until the lock is released).lock --reason <text>
- Obtain the deployment lock with a reason (will persist until the lock is released).lock <environment>
- Obtain the deployment lock for the specified environment (will persist until the lock is released).lock <environment> --reason <text>
- Obtain the deployment lock for the specified environment with a reason (will persist until the lock is released).lock --global
- Obtain a global deployment lock (will persist until the lock is released) - Blocks all environments.lock --global --reason <text>
- Obtain a global deployment lock with a reason (will persist until the lock is released) - Blocks all environments.unlock
- Release the deployment lock (if one exists).unlock <environment>
- Release the deployment lock for the specified environment (if one exists).unlock --global
- Release the global deployment lock (if one exists).lock --details
- Show information about the current deployment lock (if one exists).lock <environment> --details
- Get information about the current deployment lock for the specified environment (if one exists).lock --global --details
- Show information about the current global deployment lock (if one exists).wcid
- Alias for .lock --details
These are the available environments for this Action as defined by the inputs provided to this Action.
Note: Just because an environment is listed here does not mean it is available for deployment
production
- The default environment for this Actionproduction
- The environment that is considered "production"production,development,staging
- The list of environments that can be targeted for deploymentThe following set of examples use this Action's inputs to show you how to use the commands.
.deploy
- Deploy this branch to the production
environment.deploy main
- Rollback the production
environment to the main
branch.noop
- Deploy this branch to the production
environment in noop mode.deploy to <production|development|staging>
- Deploy this branch to the specified environment (note: the to
keyword is optional).lock <production|development|staging>
- Obtain the deployment lock for the specified environment.unlock <production|development|staging>
- Release the deployment lock for the specified environment.lock <production|development|staging> --details
- Get information about the deployment lock for the specified environmentThe following configuration options have been defined for this Action:
reaction: eyes
- The GitHub reaction icon to add to the deployment comment when a deployment is triggeredupdate_branch: warn
- This Action will warn if the branch is out of date with the base branchrequired_contexts: false
- There are no designated required contexts for this Action (default and suggested)allowForks: true
- This Action will not run on forked repositoriesskipCi: false
- This Action will require passing CI for all environmentsskipReviews: false
- This Action will require passing reviews for all environmentsdraft_permitted_targets: false
- This Action will not draft pull requests to be deployed to any environmentadmins: grantbirki
- This Action will allow the listed admins to bypass pull request reviews before deploymentpermissions: write,maintain,admin
- The acceptable permissions that this Action will require to runView the full usage guide here for additional help
Branch Deploy Demo 📹
This pull request demonstrates how to use to
github/branch-deploy
Action