Automate Release Docs subteam's Branch Syncs of the k8s website

[drewhagen]

Feature Request:

Automate the branch syncs that the Release Team’s Docs sub-team performs on the k8s website during the release cycle.

Background:

Currently, Release Docs manually merges the main branch of the website repo into the dev-<next-release> branch weekly, then pushes and opens a PR. This process involves multiple command line steps that could be automated with scripts, GitHub Actions, or other tools. Manual intervention would only be needed for merge conflicts.

Proposal:

Automate this routine so that a bot creates the PR, and Release Docs only needs to approve it or resolve conflicts.

Why This is Needed:

This process is recurring toil and can be confusing, especially for first-time contributors shadowing SIG Release, particularly those from less technical backgrounds. Automating it would reduce the burden and make contributing more accessible.

Additional Notes:

This idea has been discussed in previous cycles, but I’m unsure of the current status. I’m opening this issue to track it in our backlog.

(Not sure if feature request was the right template to use for this, so I'm open to feedback. 😄)

[vishnuswmech]

@drewhagen I like to work on this task.

Need to get the current status/needs. Can you let me know, who can help on this?

[vishnuswmech]

/assign vishnuswmech

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue 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.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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.