kubernetes / kubernetes/release

Make `krel fast-forward` work for other repositories like k/website

Open
#3,380 23 comments 0 reactions 1 assignee Claimed by @cpanato View on GitHub
area/release-eng kind/feature lifecycle/frozen priority/important-longterm sig/release
Dominant language
Go
Stars
504
Forks
556
Avg merge
18h 43m
Merged PRs (30d)
33

Description

There is a sync job in place which fast-forwards the kubernetes/kubernetes `release-1.x` branch from `master` until the final (non-prerelease) tag exists on it. The job runs periodically in prow and does basically nothing when we're not in code freeze: https://testgrid.k8s.io/sig-release-releng-blocking#git-repo-kubernetes-fast-forward

The idea is to re-use the logic for other repositories like `k/website` to sync the documentation development branch during the release cycle. We have to make the tool more flexible from a CLI perspective and double check the code paths for possible adaptations.

The entrypoint for the code of `krel fast-forward` is there: https://github.com/kubernetes/release/blob/master/cmd/krel/cmd/ff.go

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.