Closed rimolive closed 1 week ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: rimolive Once this PR has been reviewed and has the lgtm label, please assign juliusvonkohout for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
@rimolive please cross check with my early efforts in https://github.com/kubeflow/manifests/compare/master...issue-templates.
@hansinikarunarathne might help here as well @rimolive. She is anyway interested in the triaging and stalebot GSOC proposal. On Slack she is hansini karunarathne as well.
These issue templates for kubeflow/kubeflow are also quite interesting https://github.com/kubeflow/kubeflow/tree/master/.github
@Ayush9026 is also interested @rimolive on Slack Ayush Gupta
@rimolive and the same goes for @siddeshas07 on Slack Siddesh A S. All three have valid applications for GSOC and were interviewed by me.
Let's discuss in the next manifests WG about this PR. I'll add in the meeting notes.
/assign @hansinikarunarathne
@juliusvonkohout: GitHub didn't allow me to assign the following users: hansinikarunarathne.
Note that only kubeflow members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
superseded by https://github.com/kubeflow/manifests/pull/2760
Which issue is resolved by this Pull Request: Resolves #2514
Description of your changes: Setup parameters for stalebot similar to kubeflow/pipelines repo. That way issues/PRs can stay for a relevant timeframe.
Checklist:
make generate-changed-only
make test