We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since we currently have 79 issues open (the oldest is from 2020). https://github.com/kubeflow/website/pulls
We need a way to standarize PRs and issues to be stale after x amount of time. This was mentioned during the community meeting last week.
The recommended implementation is to follow a similar implementation as the pipeline module does:
The text was updated successfully, but these errors were encountered:
Please let me know if you are ok with this, so I can proceed with the implementation @andreyvelich @mameshini @hbelmiro
Sorry, something went wrong.
Sounds good to me.
Sounds good, thanks @varodrig. Please also add message to stale PRs, similar to our Training Operator stale config: https://github.com/kubeflow/training-operator/blob/master/.github/workflows/stale.yaml#L34-L43
No branches or pull requests
Since we currently have 79 issues open (the oldest is from 2020).
https://github.com/kubeflow/website/pulls
We need a way to standarize PRs and issues to be stale after x amount of time. This was mentioned during the community meeting last week.
The recommended implementation is to follow a similar implementation as the pipeline module does:
The text was updated successfully, but these errors were encountered: