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. 😄)
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 thedev-<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. 😄)