test-infra
test-infra copied to clipboard
kubernetes
fix typo with manually deploying prow
@STRRL: 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.
Welcome @STRRL!
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. :smiley:
Hi @STRRL. 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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ameukam, STRRL
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~prow/OWNERS~~ [ameukam]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Hi @ameukam , what should I do with the label do-not-merge/blocked-paths?
The details link in https://github.com/kubernetes/test-infra/pull/26981#issuecomment-1200384667 explains why the label is applied, we should not accept this PR
/cc @listx
Can you answer this? I read through https://docs.prow.k8s.io/docs/contribution-guidelines/#updating-existing-docs but don't quite understand what steps to suggest here
I need to (sometime around this quarter) create a deprecation notice to all existing markdown files for prow in this repo, so that updating them in the new repo (per the link you added) is straightforward. For now we can just manually bypass this label --- any drift between the stuff here vs what's in the new repo can be adjusted later.
