🤖 triggering CI on branch 'release-next' after synching from upstream/main #1014
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: serverless-qe The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
1 similar comment
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: serverless-qe The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
1 similar comment
|
/retest-required |
serverless-qe
force-pushed
the
release-next
branch
from
46a69da to
a2c18ae
Compare
serverless-qe
force-pushed
the
release-next-ci
branch
from
6a3a87b to
059215e
Compare
|
New changes are detected. LGTM label has been removed. |
serverless-qe
force-pushed
the
release-next
branch
from
a2c18ae to
2725814
Compare
serverless-qe
force-pushed
the
release-next-ci
branch
from
059215e to
3773f65
Compare
|
/retest-required |
|
/test 417-e2e-oncluster-test |
|
OCF Webhook is merging this PR |
No description provided.