-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Rewrite links for environment-variable-expose-pod-information to new location #10209
Conversation
…location We have a redirect, so these links aren't broken, but we shouldn't rely on the redirect - that ends up with long chains of complicated redirects and makes validating the markdown harder.
Deploy preview for kubernetes-io-master-staging ready! Built with commit 9f85ad1 https://deploy-preview-10209--kubernetes-io-master-staging.netlify.com |
1 similar comment
Deploy preview for kubernetes-io-master-staging ready! Built with commit 9f85ad1 https://deploy-preview-10209--kubernetes-io-master-staging.netlify.com |
👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
I'm inclined to approve this but I'd like to hear opinions about changing the translated contents. We are assuming that defects in the translated contents will be fixed in the translation repo (e.g. kubernetes/kubernetes-docs/zh ) and then committed back to the main repo in batches.
However, for changes like this PR, maybe it is okay to apply it here. The assumptions are as follows:
- the maintainers of the translation site, when committing translated contents back to main repo, will have to do some rebase.
- the rebase won't be a huge pain if the batch commit is performed on a weekly or biweekly basis.
/unassign |
@tengqm I agree and I think it may be covered with @zacharysarah l10n efforts. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: zparnold 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 |
We have a redirect, so these links aren't broken, but we shouldn't
rely on the redirect - that ends up with long chains of complicated
redirects and makes validating the markdown harder.