Skip to content
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

Open
amolmote opened this issue Sep 16, 2022 · 8 comments
Open

Facing issue to find out the correct relative path of components #9060

amolmote opened this issue Sep 16, 2022 · 8 comments
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. kind/documentation Categorizes issue or PR as related to documentation.

Comments

@amolmote
Copy link
Member

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.
kui

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

@k8s-ci-robot
Copy link

@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.
kui

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.

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Sep 16, 2022
@amolmote
Copy link
Member Author

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.

@starpit
Copy link
Contributor

starpit commented Sep 16, 2022

Thanks for finding this @amolmote! It looks like this document is out of date, and in great need of a refresh.

@starpit starpit added the kind/documentation Categorizes issue or PR as related to documentation. label Sep 16, 2022
@amolmote
Copy link
Member Author

help me for this @starpit, I will try to modify this document

@starpit
Copy link
Contributor

starpit commented Sep 16, 2022

thanks for the help! a few things:

  1. we removed the Carbon Components support a few major releases back, so we can remove mention of that
  2. for the list of components, i suggest we remove the specifics. these are likely to change over time. thoughts?

@amolmote
Copy link
Member Author

amolmote commented Oct 1, 2022

@starpit , sure will remove the components which having the broken issues. will that be ok

@k8s-triage-robot
Copy link

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/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was 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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 8, 2023
@amolmote
Copy link
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. kind/documentation Categorizes issue or PR as related to documentation.
Projects
None yet
Development

No branches or pull requests

4 participants