website
website copied to clipboard
Localize some pages into Ukrainian
Work by @Andygol; I'm submitting a subset of the commits available in https://github.com/Andygol/k8s-website
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please ask for approval from sftim. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Pull request preview available for checking
Built without sensitive environment variables
| Name | Link |
|---|---|
| Latest commit | a7e1143a7840cb257c0ef6d5e4c0f4d3ffc74469 |
| Latest deploy log | https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/65df9b62c8bc6a0008ba14ea |
| Deploy Preview | https://deploy-preview-45382--kubernetes-io-main-staging.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
The PR is massive from a reviewing/approving perspective. Following the precedent set by @natalisucks's comment in #45371, please break this into smaller chunks for ease of review. /hold
@Andygol - would you be willing to open PRs that contain chunks of the work you've done in your own fork? You could base them on this PR if that's helpful.
@sftim thank you for your attempt to help with the publication of the Ukrainian translation. It would be really cool if the pilot https://github.com/kubernetes/website/issues/45756 was based on my translation fork (https://github.com/Andygol/k8s-website/tree/main-uk-wip), it could solve the current problems with review and splitting the translation into separate parts.
We'll base the pilot on this repository, https://github.com/kubernetes/website
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-sigs/prow repository.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle rotten - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/close
@sftim: Closed this PR.
In response to this:
/close
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-sigs/prow repository.
@sftim thank you for your attempt to help with the publication of the Ukrainian translation. It would be really cool if the pilot #45756 was based on my translation fork (https://github.com/Andygol/k8s-website/tree/main-uk-wip), it could solve the current problems with review and splitting the translation into separate parts.
@Andygol if you send in your contributions via a PR - even a massive one that we can't merge - and you confirm your willingness to license the localization via your existing CLA, we can adapt the work you've done.
If you don't confer that agreement, we can't use it. So we'd really like to have it via a PR.
Ideally small merge-able PRs, but failing that one big one is still helpful.