Template Repository

[lunny]

A repository could be a template repository.

• You can change a normal repository from or to a template repository.
• You could do anything with a template repository like you do that with a normal repository.
• When creating a new repository, there is a list of template repositories you have permission to visit. You can pick up one and click create, and then you can chose which template repository's items (git/wiki/labels/issues/prs/settings/hooks) will be copied to new repository.
• You could use variable replacement on template repository's files. Template Repository #7365 (comment)

This will replace #2062 #7359 .

[silverwind]

Feature idea: Variable replacement in a template repo's file. For example, variables such as:

• {{REPO_NAME}}
• {{REPO_OWNER}}
• {{REPO_HTTPS_URL}}
• {{REPO_SSH_URL}}

These variables could be one-time replaced at creation time. As far as I know, GitHub's template feature does not support such a feature yet.

Copying non-git content should be optional. It brings problem of what to do with absolute URLs that point to the template repo itself. Not sure we should even attempt to rewrite those.

[davidsvantesson]

Feature idea: Variable replacement in a template repo's file.

Current readme template already support {Name} and {Description}. I think it should be the same variable replacement for template repos but in all md files (and possibly other file types as well, maybe configurable)

Copying non-git content should be optional. It brings problem of what to do with absolute URLs that point to the template repo itself. Not sure we should even attempt to rewrite those.

I agree it would be error prone to try to fix URLs, but instead more generic variables could be added to settings. For example the External Issue Tracker URL Format already support placeholders {user}, {repo} and {index}.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[davidsvantesson]

Too good idea to be closed. 💚

[jolheiser]

When creating a new repository, there is a list of template repositories you have permission to visit.

That could be quite a large list (especially for admins). Why not do it how GitHub does, where it's a Generate using this template button on the template's page?

all template repoisitory's conent (git/wiki/labels/issues/prs/settings/hooks) will be copied to new repository

I agree with @silverwind that only git content should be copied (at least at first?)
When creating a new repo using a template, the screen to create the repo could be almost identical to making a new bare repo. You can name it, make it private or not, and give it a description.
Since most of the init things would be taken care of by the template, the only other field I can think of is adding a label set at creation time, but in my opinion this should be a field when creating, not carried over from template.
Issues/PRs don't make sense to copy (in my opinion) because those would be issues/PRs towards the template, not necessarily the project you are using the template for.

[guillep2k]

Wikis and avatars are things that could come from templates as well. I use repo avatars to convey the type of repo it is (e.g. library, utility, firmware related, electronic, mechanical, etc.).

IMHO this function could be emulated by a migration from the same instance. The admin/org owner can have as many template repos as they want and clone them by migration gitea-to-gitea. It would be cool if Gitea would let you choose what items not to migrate (e.g. not issues or not teams).

[davidsvantesson]

That could be quite a large list

It can be made searchable, but I agree it is a good idea to at least allow selecting directly on the template repo.

It would be good to allow selecting what content you want to copy (or not copy) from the template repo.

[jolheiser]

• Git Content Template Repositories #8768
• Git Hooks Add git hooks and webhooks to template repositories; move to services #8926
• Webhooks Add git hooks and webhooks to template repositories; move to services #8926
• Topics Template Repositories #8768
• Auto-Expand specified variables
• Avatar
• Issue Labels
• Wiki
• Issues/PRs (in my opinion these shouldn't be part of a template generation)
• Teams, contributors if new repo owner == template owner.
• Branch protection settings (i.e. protection status; white lists too if new repo owner==tmpl owner)
• Protect branch rules (for default branch)
• Repo permissions
• Squash the commits. When create a repository from a template repository. We may want to squash all the commits on the template repository as one commit may has a default commit log init project. And the author and committer is the repository creator. (hesitation)

[guillep2k]

Started at #8768
Not closing this issue with the PR because it doesn't implement all the use-cases here.

@jolheiser I'd add to that list:

• Teams, contributors if new repo owner == template owner.
• Branch protection settings (i.e. protection status; white lists too if new repo owner==tmpl owner)
• Single (default) vs. all branches

[davidsvantesson]

Some more to make the list complete:

• Webhooks
• Topics
• Releases (Maybe not very useful?)

[lunny]

• Protect branch rules
• Repository permissions