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

A new command to list and extract template files #9413

Closed
lunny opened this issue Dec 18, 2019 · 1 comment · Fixed by #9982
Closed

A new command to list and extract template files #9413

lunny opened this issue Dec 18, 2019 · 1 comment · Fixed by #9982
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@lunny
Copy link
Member

lunny commented Dec 18, 2019

When you want to customize your templates, you have to go to find source and download them. And also the same version. When you are in a stable version, you could find it easy. But for a dev branch, it's not as easy as before.

Since all templates has been embedded in binary, if we can list them and extract them. That's better.

update:

Maybe we could extract template files from a gitea sub command like

gitea resource list
gitea resource view templates/repo/migrating
gitea resource extract templates/repo/migrating

Then it will load the special template file from binary embbed resources to current directory.

update:
I rename template to resource so that we could also view/extract js/css files to inspect purpose.

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Dec 18, 2019
@sapk
Copy link
Member

sapk commented Dec 18, 2019

Just for context, I will link the issue where this was also discussed: #9320 (comment)

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants