Starting today, we are enabling administrators to bypass all protection rules on a given environment (break glass) and force the pending jobs referencing the environment to proceed.
For more information, visit Using environments for deployment.
Starting today, we are enabling administrators to bypass all protection rules on a given environment (break glass) and force the pending jobs referencing the environment to proceed.
For more information, visit Using environments for deployment.
You can now require a successful deployment of a branch before its pull request can be merged. This is made possible by a new branch protection setting titled Require deployments to succeed before merging. To enable the setting, create a new branch protection rule for the target branch. Then, select the environments where deployments must succeed before a pull request can be merged, shown here:
This will allow you to ensure code is, for example, exercised in a staging or test environment before it's merged to your main branch.
Learn more about protected branches
Learn more about branch protection rules
Deployment review notifications for your GitHub Actions environments can now be tracked end-to-end using the GitHub app for Microsoft Teams or Slack. You will be notified when a review is pending on your environment, when an approval is completed and you can see the real time status of your deployment.
The following capabilities have been added to our Microsoft Teams and Slack applications:
For more information visit the GitHub app guidance for Microsoft Teams or for Slack