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

kubernetes / release

Release infrastructure for Kubernetes and related components

Apache License 2.0

485 stars 502 forks source link

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

Open saschagrunert opened 10 months ago

saschagrunert commented 10 months ago

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

saschagrunert commented 10 months ago

@cpanato volunteered to work on this

/assign @cpanato

cpanato commented 10 months ago

this will require some code changes I will start working on this part

cpanato commented 7 months ago

not yet done /reopen

k8s-ci-robot commented 7 months ago

@cpanato: Reopened this issue.

In response to [this](https://github.com/kubernetes/release/issues/3380#issuecomment-1940695753): >not yet done >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

k8s-triage-robot commented 4 months ago

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

cpanato commented 4 months ago

/remove-lifecycle stale

k8s-triage-robot commented 1 month ago