ci(mergify): fix deployment integ success check

[Abogical]

Reason for this change

Name was incorrectly configured.

Description of changes

Name is fixed.

Describe any new or updated permissions being added

No new permissions are added.

Description of how you validated changes

Check works on my fork using the mergify dashboard.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[Abogical]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[Abogical]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[Abogical]

@Mergifyio update

[mergify]

update

☑️ Nothing to do, the required conditions are not met

• #commits-behind > 0 [📌 update requirement]
• -closed [📌 update requirement]
• -conflict [📌 update requirement]
• queue-position = -1 [📌 update requirement]

[Abogical]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[Abogical]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[Abogical]

@Mergifyio update

[mergify]

update

☑️ Nothing to do, the required conditions are not met

• #commits-behind > 0 [📌 update requirement]
• -closed [📌 update requirement]
• -conflict [📌 update requirement]
• queue-position = -1 [📌 update requirement]

[Abogical]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.