Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Prow to v20221220-5c7fbe528a #3654

Merged

Conversation

knative-prow-updater-robot
Copy link
Contributor

Multiple distinct gcr.io/k8s-prow/ changes:

Commits Dates Images
kubernetes/test-infra@59943c5...5c7fbe5 2022‑12‑16 → 2022‑12‑20 branchprotector, checkconfig, cherrypicker, clonerefs, commenter, config-bootstrapper, configurator, crier, deck, entrypoint, generic-autobumper, ghproxy, hook, horologium, initupload, label_sync, mkpj, needs-rebase, peribolos, prow-controller-manager, sidecar, sinker, status-reconciler, tide

No gcr.io/k8s-staging-boskos/ changes.

/cc

Multiple distinct gcr.io/k8s-prow/ changes:

Commits | Dates | Images
--- | --- | ---
kubernetes/test-infra@59943c5...5c7fbe5 | 2022‑12‑16 → 2022‑12‑20 | branchprotector, checkconfig, cherrypicker, clonerefs, commenter, config-bootstrapper, configurator, crier, deck, entrypoint, generic-autobumper, ghproxy, hook, horologium, initupload, label_sync, mkpj, needs-rebase, peribolos, prow-controller-manager, sidecar, sinker, status-reconciler, tide

No gcr.io/k8s-staging-boskos/ changes.
@knative-prow
Copy link

knative-prow bot commented Dec 26, 2022

@knative-prow-updater-robot: GitHub didn't allow me to request PR reviews from the following users: knative-prow-updater-robot.

Note that only knative members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

Multiple distinct gcr.io/k8s-prow/ changes:

Commits Dates Images
kubernetes/test-infra@59943c5...5c7fbe5 2022‑12‑16 → 2022‑12‑20 branchprotector, checkconfig, cherrypicker, clonerefs, commenter, config-bootstrapper, configurator, crier, deck, entrypoint, generic-autobumper, ghproxy, hook, horologium, initupload, label_sync, mkpj, needs-rebase, peribolos, prow-controller-manager, sidecar, sinker, status-reconciler, tide

No gcr.io/k8s-staging-boskos/ changes.

/cc

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@knative-prow knative-prow bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Dec 26, 2022
@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jan 2, 2023
@knative-prow
Copy link

knative-prow bot commented Jan 2, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: knative-prow-updater-robot, upodroid

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 2, 2023
@upodroid
Copy link
Member

upodroid commented Jan 3, 2023

/override "style / suggester / shell"
/override "style / suggester / yaml"

@knative-prow
Copy link

knative-prow bot commented Jan 3, 2023

@upodroid: Overrode contexts on behalf of upodroid: style / suggester / shell, style / suggester / yaml

In response to this:

/override "style / suggester / shell"
/override "style / suggester / yaml"

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@knative-prow knative-prow bot merged commit 7fdb48e into knative:main Jan 3, 2023
@knative-prow
Copy link

knative-prow bot commented Jan 3, 2023

@knative-prow-updater-robot: Updated the following 2 configmaps:

  • config configmap in namespace default at cluster default using the following files:
    • key config.yaml using file prow/config.yaml
  • job-config configmap in namespace default at cluster default using the following files:
    • key autobump-flaky-test-reporter.yaml using file prow/jobs/custom/autobump-flaky-test-reporter.yaml
    • key autobump-prow-tests.yaml using file prow/jobs/custom/autobump-prow-tests.yaml
    • key autobump-prow.yaml using file prow/jobs/custom/autobump-prow.yaml
    • key autodeploy-prow.yaml using file prow/jobs/custom/autodeploy-prow.yaml
    • key branchprotector.yaml using file prow/jobs/custom/branchprotector.yaml
    • key label-sync.yaml using file prow/jobs/custom/label-sync.yaml
    • key peribolos.yaml using file prow/jobs/custom/peribolos.yaml
    • key stale.yaml using file prow/jobs/custom/stale.yaml
    • key test-infra.yaml using file prow/jobs/custom/test-infra.yaml

In response to this:

Multiple distinct gcr.io/k8s-prow/ changes:

Commits Dates Images
kubernetes/test-infra@59943c5...5c7fbe5 2022‑12‑16 → 2022‑12‑20 branchprotector, checkconfig, cherrypicker, clonerefs, commenter, config-bootstrapper, configurator, crier, deck, entrypoint, generic-autobumper, ghproxy, hook, horologium, initupload, label_sync, mkpj, needs-rebase, peribolos, prow-controller-manager, sidecar, sinker, status-reconciler, tide

No gcr.io/k8s-staging-boskos/ changes.

/cc

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. skip-review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants