kubernetes
CAPO: add apidiff optional job
Add a new job to run apidiff on CAPO main PRs.
TODO:
- [ ] Get https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/2096
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: EmilienM Once this PR has been reviewed and has the lgtm label, please assign fabriziopandini for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
We need https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/2096 first.
Related to https://github.com/kubernetes-sigs/cluster-api-provider-openstack/issues/1860
We need kubernetes-sigs/cluster-api-provider-openstack#2096 first.
Can you put this dependency in the description as a TODO item?
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
I'll re-open this one when we'll want to have it. For now we don't have the desire of gating apidiff.
@EmilienM: Closed this PR.
In response to this:
/close
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.