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

Prow test force reload #28076

Closed
wants to merge 521 commits into from
Closed

Conversation

pgodowski
Copy link

No description provided.

horis233 and others added 30 commits August 19, 2020 09:52
* Allow development jobs

* License Service development prow job

* revert License Service master branch prow job
* fix multiarch image build for ibm-elastic-stack-operator.

* fix lint issue.
* add new reviewers and approvers.

* remove inactive owners.
* audit - use build tool for coverage

* add entrypoint
@k8s-ci-robot
Copy link
Contributor

@pgodowski: Adding label: do-not-merge/blocked-paths because PR changes a protected file.

Reasons for blocking this PR:

[All Prow documentation (Markdown files) have moved to https://github.com/kubernetes-sigs/prow as part of https://github.com/kubernetes-sigs/prow/issues/4. Instructions for updating existing docs are at https://docs.prow.k8s.io/docs/contribution-guidelines/#updating-existing-docs.]

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.

@k8s-ci-robot k8s-ci-robot added do-not-merge/blocked-paths Indicates that a PR should not merge because it touches files in blocked paths. do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. labels Nov 21, 2022
@k8s-ci-robot
Copy link
Contributor

Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages.

The list of commits with invalid commit messages:

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. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 21, 2022
@k8s-ci-robot
Copy link
Contributor

@pgodowski: PR needs rebase.

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.

@k8s-ci-robot
Copy link
Contributor

Welcome @pgodowski!

It looks like this is your first PR to kubernetes/test-infra 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/test-infra has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Nov 21, 2022
@k8s-ci-robot
Copy link
Contributor

Hi @pgodowski. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@k8s-ci-robot k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Nov 21, 2022
@pgodowski pgodowski closed this Nov 21, 2022
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pgodowski
Once this PR has been reviewed and has the lgtm label, please assign bentheelder for approval by writing /assign @bentheelder in a comment. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

@k8s-ci-robot k8s-ci-robot added area/config Issues or PRs related to code in /config area/gopherage Issues or PRs related to code in /gopherage labels Nov 21, 2022
@k8s-ci-robot k8s-ci-robot added area/gubernator Issues or PRs related to code in /gubernator area/jobs area/prow Issues or PRs related to prow area/prow/deck Issues or PRs related to prow's deck component area/prow/plugins Issues or PRs related to prow's plugins for the hook component area/prow/spyglass Issues or PRs related to prow's spyglass UI area/prow/tide Issues or PRs related to prow's tide component sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Nov 21, 2022
@linux-foundation-easycla
Copy link

CLA Missing ID CLA Not Signed

@ashank07 ashank07 deleted the prow-test-force-reload branch December 3, 2024 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/config Issues or PRs related to code in /config area/gopherage Issues or PRs related to code in /gopherage area/gubernator Issues or PRs related to code in /gubernator area/jobs area/prow/deck Issues or PRs related to prow's deck component area/prow/plugins Issues or PRs related to prow's plugins for the hook component area/prow/spyglass Issues or PRs related to prow's spyglass UI area/prow/tide Issues or PRs related to prow's tide component area/prow Issues or PRs related to prow do-not-merge/blocked-paths Indicates that a PR should not merge because it touches files in blocked paths. do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.