Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Template Repository #9126

Open
8 of 15 tasks
jolheiser opened this issue Nov 22, 2019 · 16 comments
Open
8 of 15 tasks

Template Repository #9126

jolheiser opened this issue Nov 22, 2019 · 16 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/summary This issue aggregates a bunch of other issues

Comments

@jolheiser
Copy link
Member

jolheiser commented Nov 22, 2019

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:

Implemented after 1.11.0/unknown:

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

@guillep2k
Copy link
Member

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

@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Nov 23, 2019
@lunny
Copy link
Member

lunny commented Nov 23, 2019

Are all branches of the git repository moved?

@lunny lunny mentioned this issue Nov 23, 2019
4 tasks
@jolheiser
Copy link
Member Author

jolheiser commented Nov 23, 2019

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
Copy link

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

@jolheiser
Copy link
Member Author

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

@dharmann
Copy link

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

@bmackinney
Copy link

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
Copy link

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
Copy link
Member

lunny commented May 7, 2020

@joshbalfour Could you fire a bug issue?

@stale
Copy link

stale bot commented Jul 6, 2020

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
Copy link

stale bot commented Jul 20, 2020

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

@stale stale bot closed this as completed Jul 20, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
@go-gitea go-gitea unlocked this conversation Jan 13, 2021
@jolheiser jolheiser added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Jan 13, 2021
@jolheiser jolheiser reopened this Jan 13, 2021
@chris-NR
Copy link

chris-NR commented Apr 7, 2021

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)

@lunny lunny added the type/summary This issue aggregates a bunch of other issues label Apr 19, 2021
@clarfonthey
Copy link
Contributor

clarfonthey commented Feb 5, 2022

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.

@twisted-nematic57
Copy link

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).
edited Screenshot from 2023-01-07 16-41-30

@bendem
Copy link

bendem commented Mar 8, 2023

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.

image

@theAkito
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/summary This issue aggregates a bunch of other issues
Projects
None yet
Development

No branches or pull requests