Facing issue to find out the correct relative path of `components`
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
@amolmote: This request has been marked as needing help from a contributor.
Guidelines
Please ensure that the issue body includes answers to the following questions:
- Why are we solving this issue?
- To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
- Does this issue have zero to low barrier of entry?
- How can the assignee reach out to you for help?
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
by commenting with the /remove-help command.
In response to this:
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
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:
- we removed the Carbon Components support a few major releases back, so we can remove mention of that
- for the list of components, i suggest we remove the specifics. these are likely to change over time. thoughts?
@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:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale