REQUEST: Create devcontainers-builds repository

[Sharpz7]

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

Who should have admin access?

sharpz7, craiglpeters, other members of https://github.com/kubernetes/community/blob/master/sig-contributor-experience/README.md#chairs as required

Who should have write access?

sharpz7, craiglpeters, other members of https://github.com/kubernetes/community/blob/master/sig-contributor-experience/README.md#chairs as required

Who should be listed as approvers in OWNERS?

sharpz7, craiglpeters, other members of https://github.com/kubernetes/community/blob/master/sig-contributor-experience/README.md#chairs as required

Who should be listed in SECURITY_CONTACTS?

sharpz7, craiglpeters, other members of https://github.com/kubernetes/community/blob/master/sig-contributor-experience/README.md#chairs as required

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: kubernetes/kubernetes#113019
And this PR: kubernetes/kubernetes#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: kubernetes/kubernetes#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]

xref: kubernetes/test-infra#30454 (comment)

[k8s-triage-robot]

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]

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]

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]

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

In response to this:

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

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.