Adding label:do-not-merge because PR changes docs prohibited to auto merge
See http://kubernetes.io/editdocs/ for information about editing docs

@kubernetes/docs-review-team Is the do-not-merge label correct?
I assume that the latest autogenerated copy still remains in this repo and then we pull it periodically in kubernetes.github.io.

the bot is correct

@eparis since the docs are auto-generated, should the bot allow this PR to be merged but keep the kind/old-docs label like how it treats kubectl PRs which also contain auto-generated docs?

@k8s-bot e2e test this issue: #26138

@k8s-bot node e2e test this issue: #26203

Discussed this with @bgrant0607 and he agreed that it is fine to add autogenerated docs to this repo. We will need to manually merge the PR.
We want to move autogenerated docs to the new docs repo but havent done that yet.

As @janetkuo said, it will be good to make the bot smarter to recognize these auto generated docs and handle them as a special case.

GCE e2e build/test passed for commit 060e537.

• Build Log
• Test Artifacts
• Internal Jenkins Results

sorry, I completely missed they are auto-generated. We need to update https://github.com/kubernetes/contrib/blob/master/mungegithub/block-path.yaml

@eparis Thanks for fixing the bot!
Can I have LGTM? :)

Adding label:do-not-merge because PR changes docs prohibited to auto merge
See http://kubernetes.io/editdocs/ for information about editing docs

@eparis Do we need to do something for kubernetes-retired/contrib#1072 to take effect?
merge bot is still adding do-not-merge label.

LGTM. blocked until submit-queue is restarted, and i'm not going to restart it since it is making progress.

@eparis @nikhiljindal this broke the build... fixed in #26400