fix(apigateway): use deployed stage's name when using MonitoringAspect #409
Mergify / Summary
succeeded
Aug 10, 2023 in 1s
2 potential rules
Rule: Automatic merge on approval and successful build (delete_head_branch)
-
-label~=(do-not-merge)
-
#approved-reviews-by>=1
-
closed
[:pushpin: delete_head_branch requirement] -
status-success=build
-
status-success=package-dotnet
-
status-success=package-java
-
status-success=package-js
-
status-success=package-python
Rule: Automatic merge on approval and successful build (queue)
-
-label~=(do-not-merge)
-
#approved-reviews-by>=1
-
-draft
[:pushpin: queue requirement] -
-mergify-configuration-changed
[:pushpin: queue -> allow_merging_configuration_change setting requirement] -
status-success=build
-
status-success=package-dotnet
-
status-success=package-java
-
status-success=package-js
-
status-success=package-python
- any of: [:twisted_rightwards_arrows: queue conditions]
- all of: [:pushpin: queue conditions of queue
default
]-
#approved-reviews-by>=1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection]
-
- all of: [:pushpin: queue conditions of queue
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branch
Additionally, on Mergify dashboard you can:
- look at your merge queues
- generate the Mergify configuration with the config editor.
Finally, you can contact us on https://mergify.com
Loading