Update milestone applier for k/website dev-1.36 release branch

[Urvashi0109]

Update the k/website milestone applier for the dev-1.36 branch to automatically apply the 1.36 milestone for PRs created against the dev-1.36 branch.

/hold for review from @kubernetes/sig-docs-leads

[Copilot]

Pull request overview

This PR updates the milestone applier configuration for the kubernetes/website repository to support the new dev-1.36 release branch by configuring automatic application of the 1.36 milestone for PRs created against the dev-1.36 branch.

• Updates the kubernetes/website milestone applier configuration from dev-1.35 to dev-1.36

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Urvashi0109]

/assign @reylejano

[dipesh-rawat]

/lgtm

[Urvashi0109]

/assign @Priyankasaggu11929

[Priyankasaggu11929]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Priyankasaggu11929, Urvashi0109

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• config/OWNERS [Priyankasaggu11929]

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

[Priyankasaggu11929]

Keeping the unhold part to SIG Docs Lead or Release Docs Team. Thanks!

[Urvashi0109]

/assign @MadhavJivrajani

[natalisucks]

/lgtm from docs, thanks!

[Priyankasaggu11929]

/lgtm from docs, thanks!

/unhold

[k8s-ci-robot]

@Urvashi0109: Updated the plugins configmap in namespace default at cluster test-infra-trusted using the following files:

• key plugins.yaml using file config/prow/plugins.yaml

Details

In response to this:

Update the k/website milestone applier for the dev-1.36 branch to automatically apply the 1.36 milestone for PRs created against the dev-1.36 branch.

/hold for review from @kubernetes/sig-docs-leads

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.