Template Repository

[jolheiser]

Continues #7365 with a new issue so I can more closely update the head description as things are implemented/changed.

Hopefully implemented by 1.11.0:

• Git Content Template Repositories #8768
• Topics 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
• Avatar Add avatar and issue labels to template repositories #9149
• Issue Labels Add avatar and issue labels to template repositories #9149
• Auto-Expand specified variables 1 2 Variable expansion in repository templates #9163 More expansions in template repositories #10021

Implemented after 1.11.0/unknown:

• Wiki
• Issues/PRs (in my opinion these shouldn't be part of a template generation)
• Teams, contributors if new repo owner == template owner.
• Branches/Protection Rules 1
• 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)
• API support FR: Creating a repo from a template repo via API #15934
• Expand file/directory names Template files/directories with customisable names #14273

Feel free to suggest more to add to this list, or changes to this list.

[guillep2k]

Mm.... This calls for a voting system embedded in Gitea. 🤔 😁

[lunny]

Are all branches of the git repository moved?

[jolheiser]

Are all branches of the git repository moved?

Currently only default branch is copied, although @guillep2k has proposed some use-cases I linked in the above list that might be beneficial.

[dharmann]

I'm trying to create a repo template. Is there some documentation explaining hot to do that?
Thanks!

[jolheiser]

It is a setting in your repository. Keep in mind this feature is available only in 1.11+

[dharmann]

It is a setting in your repository. Keep in mind this feature is available only in 1.11+
Thanks so much!

[bmackinney]

Instead of copying the parent project Issues/PR's, I'd find utility in defining default Issues in files, perhaps like .gitea/template_issues/01-initialize-project.md - to provide child projects with the same set of checklists to complete and decisions to discuss and document. These files could contain yaml or toml frontmatter for processing into issue variables, and markdown bodies for the initial description.
Once templates copy branches, .gitea/template_PRs/01-begin-project.md could follow the same pattern but can include branch names in the frontmatter. Both directories could be excluded from the child project, like .gitea/template is.

[joshbalfour]

please don't forget to fire the push webhook when a repository is created from a template! just noticed that it's not atm

[lunny]

@joshbalfour Could you fire a bug issue?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

[stale]

This issue has been automatically closed because of inactivity. You can re-open it if needed.

[chris-NR]

A few additional suggestions:

• Provide a default template setting (at service level and/or at organization level)
• Use this setting when push-to-create is enabled (or allow template as a push option?)
• Set initial tab (currently always "Code" but could be "Issues", "Projects" etc)

[clarfonthey]

Something that I find useful that I haven't seen so far: it would be nice to be able to require custom variables on the template that the user has to fill out, which then get expanded in the .gitea/template files. For example, a repo may want to have both an identifier (${REPO_NAME}) and a proper "name" string which may contain spaces or other characters. Even if repo names could contain any character, this would still be desirable, imho.

[HackerDaGreat57]

I think it would also be great if it was possible to copy milestones and projects too, along with the wiki @jolheiser already suggested. (I created a template on my instance complete with project, milestone and template wiki, and was then disappointed I would have to copy it manually 😆)

---

Mm.... This calls for a voting system embedded in Gitea. thinking grin

@guillep2k I think the best way to implement that would be to make a Discussions tab in Gitea (just like there is in Github) and then make a "polls" section in that (again, just like Github).

[bendem]

Would be great if you could select settings to be copied over when creating from a template.

We want our merge strategies to be consistent across repos, wiki and issues are external so we want this to be ported too. It's a bunch of checkboxes that have to be verified for every new repo.

Another solution is to make that configuration available at the org level. That what bitbucket does, it's great.

[theAkito]

Was about to suggest the same as @bendem did. I hoped, there'd be a global (or organisation wide - both would be great) default branch protection setting. For example, if I want the master branch to be protected, by default, so the repository owner has to specifically disable this to enable force pushes, etc.