-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
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
Add a hugo template to highlight minimum supported version #2325
Comments
/good-first-issue |
@alculquicondor: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Hi @alculquicondor, I would like to work on this. I'm new to the project and will appreciate some guidance on how to go about this. |
You can probably look at this PR for inspiration #2006 To see your work locally, you can run |
/assign |
@alculquicondor is there somewhere that we need to use this block right now? To test this I just added it to a random page but didn't commit this change. This is how it looks like. It also looks like I didn't configure my git properly so it didn't use my actual email address and the bots say I didn't sign the license agreement. Would it be okay to edit that commit and force push to my branch or should I close the current PR and create a new one? |
@ivange94 We're ok with either way. |
We aim to replace the warnings/notes like the ones below. https://kueue.sigs.k8s.io/docs/tasks/manage/setup_sequential_admission/#requeuing-strategy |
What would you like to be added:
Some reusable block that looks similar to the following:
And then use that for every time we mention that a feature is only available in a certain version.
Why is this needed:
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.
The text was updated successfully, but these errors were encountered: