-
Notifications
You must be signed in to change notification settings - Fork 185
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
Facing issue to find out the correct relative path of components
#9060
Comments
@amolmote: 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/test-infra repository. |
If this file is not exists and work in progress then i think we should provide the basic template of that file to that relative locations. |
Thanks for finding this @amolmote! It looks like this document is out of date, and in great need of a refresh. |
help me for this @starpit, I will try to modify this document |
thanks for the help! a few things:
|
@starpit , sure will remove the components which having the broken issues. will that be ok |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Someone correct me If I am wrong.
I have observed issue in this components.md file.
when I clicked on the some of components, these links are not working properly.
Then I have tried to find out its correct relative path in the respective directory then I did not get anything.
someone please help me to point to the correct location of these files.
/assign
/kind bug
/help
The text was updated successfully, but these errors were encountered: