REQUEST: Create devcontainers-builds repository

Sharpz7 commented 11 months ago

New repo, staging repo, or migrate existing

new repository

Is it a staging repo?

no

Requested name for new repository

devcontainer-builds

Which Organization should it reside

kubernetes

What should the repo description be?

Created to hold any build configs and scripts required to use devcontainers in a k8s-owned repo.

Linked to the work of this issue: https://github.com/kubernetes/kubernetes/issues/113019 And this PR: https://github.com/kubernetes/kubernetes/pull/120551

What SIG and subproject does this fall under?

sig-contribex, sigs-github-actions

Please provide references to appropriate approval for this new repo

Slack link to Dims message to create this ticket: https://kubernetes.slack.com/archives/C1TU9EB9S/p1694451955693599?thread_ts=1694449893.136789&cid=C1TU9EB9S

Additional context for request

The PR that lead to this being created: https://github.com/kubernetes/kubernetes/pull/120551

The main k8s repo should only have a single .devcontainer config, and maybe a script file. The rest can belong here - with an image being created that effectively does the same thing.

https://github.com/craiglpeters/kubernetes-devcontainer was set up this way as a proof of concept. The configs and code in .github is what will belong in here.

BenTheElder commented 11 months ago

xref: https://github.com/kubernetes/test-infra/issues/30454#issuecomment-1714592279

k8s-triage-robot commented 7 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 6 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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 issue is closed

You can:

Reopen this issue with /reopen
Mark this issue as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 5 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/org/issues/4468#issuecomment-2026697053): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues 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 issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

kubernetes / org