search

kubernetes-sigs / prow

Prow is a Kubernetes based CI/CD system developed to serve the Kubernetes community. This repository contains Prow source code and Hugo sources for Prow documentation site.
https://docs.prow.k8s.io
Apache License 2.0
115 stars 95 forks source link

Migrate Prow-related labels from `k/t-i` repo #111

Open jihoon-seo opened 6 months ago

jihoon-seo commented 6 months ago

It would be great to migrate Prow-related labels from k/t-i repo.

[As-is] According to https://github.com/kubernetes/test-infra/blob/master/label_sync/labels.yaml, These labels exist in kubernetes/test-infra repo:

  1. area/prow
  2. area/prow/branchprotector
  3. area/prow/bump
  4. area/prow/clonerefs
  5. area/prow/crier
  6. area/prow/config-bootstrapper
  7. area/prow/deck
  8. area/prow/entrypoint
  9. area/prow/gcsupload
  10. area/prow/gerrit
  11. area/prow/hook
  12. area/prow/horologium
  13. area/prow/initupload
  14. area/prow/jenkins-operator
  15. area/prow/knative-build
  16. area/prow/mkpj
  17. area/prow/mkpod
  18. area/prow/peribolos
  19. area/prow/phony
  20. area/prow/plank (Note: plank has been deprecated.)
  21. area/prow/plugins
  22. area/prow/pubsub
  23. area/prow/sidecar
  24. area/prow/sinker
  25. area/prow/splice
  26. area/prow/status-reconciler
  27. area/prow/spyglass
  28. area/prow/tide
  29. area/prow/tot
  30. area/prow/pod-utilities

[Option 1] Migrate Prow-related labels as-is:

  1. area/prow
  2. area/prow/branchprotector
  3. area/prow/bump
  4. area/prow/clonerefs
  5. area/prow/crier
  6. area/prow/config-bootstrapper
  7. area/prow/deck
  8. area/prow/entrypoint
  9. area/prow/gcsupload
  10. area/prow/gerrit
  11. area/prow/hook
  12. area/prow/horologium
  13. area/prow/initupload
  14. area/prow/jenkins-operator
  15. area/prow/knative-build
  16. area/prow/mkpj
  17. area/prow/mkpod
  18. area/prow/peribolos
  19. area/prow/phony
  20. ~area/prow/plank~ (Note: plank has been deprecated.)
  21. area/prow/plugins
  22. area/prow/pubsub
  23. area/prow/sidecar
  24. area/prow/sinker
  25. area/prow/splice
  26. area/prow/status-reconciler
  27. area/prow/spyglass
  28. area/prow/tide
  29. area/prow/tot
  30. area/prow/pod-utilities

[Option 2] Since this repo is all about Prow, so remove the prow prefix from all labels, and the area/prow label itself:

  1. ~area/prow~
  2. area/branchprotector
  3. area/bump
  4. area/clonerefs
  5. area/crier
  6. area/config-bootstrapper
  7. area/deck
  8. area/entrypoint
  9. area/gcsupload
  10. area/gerrit
  11. area/hook
  12. area/horologium
  13. area/initupload
  14. area/jenkins-operator
  15. area/knative-build
  16. area/mkpj
  17. area/mkpod
  18. area/peribolos
  19. area/phony
  20. ~area/plank~ (Note: plank has been deprecated.)
  21. area/plugins
  22. area/pubsub
  23. area/sidecar
  24. area/sinker
  25. area/splice
  26. area/status-reconciler
  27. area/spyglass
  28. area/tide
  29. area/tot
  30. area/pod-utilities

Which option seems better? Any opinions are welcome!

Note: I don't know whether label_sync is enabled for this repo (k-s/prow). If not, then we need to enable as well.

Note: We need to add OWNERS file to each directory, to enable Prow's auto-labeling. (The PR #101 affects the location of OWNERS file that will be added.)

/assign

k8s-triage-robot commented 3 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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 month ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/prow/issues/111#issuecomment-2350819571): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
petr-muller commented 1 month ago

/reopen /remove-lifecyle rotten

I'd like this (along with some other contributor experience improvements)

k8s-triage-robot commented 3 days ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 3 days ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/prow/issues/111#issuecomment-2423086957): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
petr-muller commented 19 hours ago

/reopen /remove-lifecycle rotten

k8s-ci-robot commented 19 hours ago

@petr-muller: Reopened this issue.

In response to [this](https://github.com/kubernetes-sigs/prow/issues/111#issuecomment-2426675614): >/reopen >/remove-lifecycle rotten 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.