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

Remove links to the Kubernetes repository #3361

Open
iholder101 opened this issue Apr 21, 2024 · 9 comments
Open

Remove links to the Kubernetes repository #3361

iholder101 opened this issue Apr 21, 2024 · 9 comments
Labels
help wanted Identifies an issue that has been specifically created or selected for new contributors. kind/bug lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@iholder101
Copy link
Contributor

What happened:
We have links referencing the Kubernetes repo. Example:

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.

Example: kubevirt/kubevirt#11743 (comment) (unfold the collapsed message).

What you expected to happen:
Avoid referencing Kubernetes. Reference Kubevirt instead.

@iholder101
Copy link
Contributor Author

FYI @dhiller @oshoval

@oshoval
Copy link
Contributor

oshoval commented Apr 21, 2024

we are using test-infra, we don't fork it as far as i know
the questions it mentioned is about the plugin itself, not kubevirt repo
we can't change it easily and not required due to the above reason imho
btw test-infra moved to https://github.com/kubernetes-sigs/prow

@dhiller
Copy link
Contributor

dhiller commented Apr 22, 2024

It makes sense to link to our own prow command page, since not all commands that are available for kubernetes prow bot are available for our own bot, also we have some prow external plugins that aren't available outside our org.

@dhiller
Copy link
Contributor

dhiller commented Apr 22, 2024

What we need to find out though is to where to configure the links.

@kubevirt-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 21, 2024
@kubevirt-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@kubevirt-bot kubevirt-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 20, 2024
@dhiller
Copy link
Contributor

dhiller commented Sep 17, 2024

I think that we definitely want to do this at some point.

/remove-lifecycle rotten
/lifecycle frozen

Since there's a bit of work to do, i.e. find out where to configure the links and maybe even create doc pages in the community repository, I'll not make this a good first issue - nevertheless someome from the community might be interested.

/help-wanted

@kubevirt-bot kubevirt-bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Sep 17, 2024
@dhiller
Copy link
Contributor

dhiller commented Sep 17, 2024

/help

@kubevirt-bot
Copy link
Contributor

@dhiller:
This request has been marked as needing help from a contributor.

Guidelines

  • No Barrier to Entry
  • Clear Task
  • Solution Explained
  • Provides Context
  • Identifies Relevant Code
  • Gives Examples
  • Ready to Test
  • Goldilocks priority
  • Up-To-Date

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:

/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-sigs/prow repository.

@kubevirt-bot kubevirt-bot added the help wanted Identifies an issue that has been specifically created or selected for new contributors. label Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Identifies an issue that has been specifically created or selected for new contributors. kind/bug lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

4 participants