Instruction on how to create a new repo using the operate-first/template repo about common HOT 9 CLOSED

I believe that it is possible but I think that it would require upstream contributions to Peribolos. Peribolos uses the configureOrg function to call the configureRepos function in the main.go file, which finally calls the createRepo function available in /prow/github of kubernetes/test-infra if the repo doesn't exist and is not archived. This sends a request using the https://developer.github.com/v3/repos/#create endpoint according to the documentation, which has been moved, but as far as I can tell, docs for it now live here. However, creating a repository from a template actually uses a different GitHub endpoint. For this method, you call the generate endpoint of the repository where the template actually lives, and then additionally pass the owner and name for the desired repository you are creating, along with the aforementioned template_owner and template_repo to access the template. It seems plausible to extend the repository client with a createRepoFromTemplate function, and use the github-config.yaml to track the template repository, but maybe there is an easier way around this.

from common.

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

from common.

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

from common.

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

from common.

/remove-lifecycle rotten

from common.

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

from common.

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

from common.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

from common.

@sesheta: Closing this issue.

from common.