controller-tools
controller-tools copied to clipboard
Hide `// TODO:` from generated CRD.
Would be awesome to be able to annotate each _types.go field if there is a TODO but without having it live in a CRD for end users to see.
Related: #649
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and 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 issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and 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 issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
On Sat, Jan 28, 2023, 5:52 PM Kubernetes Triage Robot < @.***> wrote:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
- Close this issue or PR with /close
- Offer to help out with Issue Triage https://www.kubernetes.dev/docs/guide/issue-triage/
Please send feedback to sig-contributor-experience at kubernetes/community https://github.com/kubernetes/community.
/lifecycle rotten
— Reply to this email directly, view it on GitHub https://github.com/kubernetes-sigs/controller-tools/issues/728#issuecomment-1407505416, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACVVG6ABKQTDD2DZTTWBRT3WUWPLTANCNFSM6AAAAAAQWDBKIM . You are receiving this because you authored the thread.Message ID: @.***>
Hi @kaovilai,
Would you like to work on a PR to propose this solution?
I'm open to it :)
On Tue, Jan 31, 2023, 4:45 AM Camila Macedo @.***> wrote:
Hi @kaovilai https://github.com/kaovilai,
Would you like to work on a PR to propose this solution?
— Reply to this email directly, view it on GitHub https://github.com/kubernetes-sigs/controller-tools/issues/728#issuecomment-1410052654, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACVVG6FYRBX3O6LVSDOOLALWVDNLLANCNFSM6AAAAAAQWDBKIM . You are receiving this because you were mentioned.Message ID: @.***>
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
/remove-lifecycle stale
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
unstale
/remove-lifecycle stale
/lifecycle frozen
I think it makes sense to strip TODOs like upstream. We don't want TODOs showing up in CRDs, especially if they are on types from k/k.