[hi] Add content/hi/docs/setup/production-environment/windows/user-guide-windows-containers.md

[arsheelsheikh]

localization
[hi] Add content/hi/docs/setup/production-environment/windows/user-guide-windows-containers.md

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign mittalyashu after the PR has been reviewed.
You can assign the PR to them by writing /assign @mittalyashu in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• content/hi/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[AvineshTripathi]

I think abbreviation should remain as it is while localising also on a overview I found these changes to be appropriate

[sftim]

Watch out for relying on automation to help with translation.

[sftim]

@arsheelsheikh would you be willing to squash this down to 1 commit (https://kubernetes.io/docs/contribute/new-content/open-a-pr/#addressing-feedback-locally has some details, and it's OK to ask more questions too)

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: arsheelsheikh / name: Arsheel Sheikh (1602913)

[arsheelsheikh]

@arsheelsheikh would you be willing to squash this down to 1 commit (https://kubernetes.io/docs/contribute/new-content/open-a-pr/#addressing-feedback-locally has some details, and it's OK to ask more questions too)

@sftim I followed the handbook and tried squashing but it seems something is wrong!

[sftim]

This change looks reasonable, commit wise. The commit message summary “hi localization” isn't as helpful as it could be.

If you can, check out the branch you've named arsheelsheikh and run git commit --amend. Now you can write a new commit message that more clearly summarises the change. For example:

Localize “Guide for scheduling Windows containers in Kubernetes” into Hindi

[jayesh-srivastava]

Hey, I noticed that this document contains a mixture of both windows and विंडोज. I guess we should stick to one only. Can you please take a look at other Hindi docs and make the change accordingly?

[anubha-v-ardhan]

Hey, I noticed that this document contains a mixture of both windows and विंडोज. I guess we should stick to one only. Can you please take a look at other Hindi docs and make the change accordingly?

We're writing it as Windows, it being a trademark of Microsoft Corporation.

[jayesh-srivastava]

Hey, I noticed that this document contains a mixture of both windows and विंडोज. I guess we should stick to one only. Can you please take a look at other Hindi docs and make the change accordingly?

We're writing it as Windows, it being a trademark of Microsoft Corporation.

That should be it then. @arsheelsheikh can you please do the needful.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[anubha-v-ardhan]

/remove-lifecycle rotten

[arsheelsheikh]

All these PR mails were sent to the spam folder due to which I missed track on this PR, just checked now

[arsheelsheikh]

should I be making fresh PR now?

[sftim]

You can update this PR @arsheelsheikh; you don't need to make a new one.

[Sea-n]

Hey @arsheelsheikh, of course you can (and you should) update this PR instead of open a new one.

But before we move on, you have to sign CLA so that the check can be pass.
/easycla

Edit: The check passed after manually refresh.

[divya-mohan0209]

Hey @arsheelsheikh , you can make changes on this PR itself OR open a fresh PR whichever is comfortable for you. Could you please do it at the earliest possible since this has been pending for ~ 1 month now?

[Sea-n]

Hey @arsheelsheikh,

Thanks for purposing this PR. But since you didn't respond for a while, we have to close this PR now.
/close

Feel free to open a fresh one (and don't forget to mention this PR) when you are ready to move forward.

[k8s-ci-robot]

@Sea-n: Closed this PR.

In response to this:

Hey @sean,

Thanks for purposing this PR. But since you didn't respond for a while, we have to close this PR now.
/close

Feel free to open a fresh one (and don't forget to mention this PR) when you are ready to move forward.

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.