Automatically create release-team-shadow-stats report that can be shared with the community

kubernetes-sigs / release-team-shadow-stats

Kubernetes release team shadow program application analysis

Apache License 2.0

14 stars 6 forks source link

Automatically create release-team-shadow-stats report that can be shared with the community #14

Closed leonardpahlke closed 2 years ago

leonardpahlke commented 2 years ago

Currently there the report structure is under discussion. After the report structure has been discussed the report will be created manually. This task to create the report manually should get automatized.

see discuss report structure issue: https://github.com/kubernetes-sigs/release-team-shadow-stats/issues/8

k8s-triage-robot commented 2 years ago

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/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 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

leonardpahlke commented 2 years ago

/remove-lifecycle stale

leonardpahlke commented 2 years ago

creating the report once per cycle is not much work, automating this process is not worth it

/close

k8s-ci-robot commented 2 years ago

@leonardpahlke: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/release-team-shadow-stats/issues/14#issuecomment-1219392128): >creating the report once per cycle is not much work, automating this process is not worth it > >/close 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.