Use git diff to check what is changed in the upstream. And apply the upstream changes manually
to the content/ko of upstream/dev-1.16-ko.6 branch.
For example:
# checkout `upstream/dev-1.16-ko.6`
...
# check what is updated in the upstream
git diff upstream/dev-1.16-ko.5 upstream/dev-1.16-ko.6 -- content/en/docs/concepts/architecture/nodes.md
# apply changes to content/ko
vi content/ko/docs/concepts/architecture/nodes.md
...
# commit and push
...
# make PR to `upstream/dev-1.16-ko.6`
In response to [this](https://github.com/kubernetes/website/issues/17755#issuecomment-560178780):
>/close
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
This is a Bug Report
Problem
Outdated files in the dev-1.16-ko.6 branch.
24 files to be modified
0 files to be renamed
0 files to be deleted
Proposed Solution
Use
git diff
to check what is changed in the upstream. And apply the upstream changes manually to thecontent/ko
ofupstream/dev-1.16-ko.6
branch.For example:
Pages to Update