github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

[PR #3051] [MERGED] Reduce overhead of upgrades for users with custom stylesheets/JS #16733

New Issue
Closed
opened 2025-11-02 12:17:42 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 12:17:42 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-gitea/gitea/pull/3051
Author: @techknowlogick
Created: 12/1/2017
Status: ✅ Merged
Merged: 12/3/2017
Merged by: @lafriks

Base: master ← Head: template_customizations

📝 Commits (5)

  • 81c9ce9 Reduce overhead of upgrades for users with custom stylesheets/JS
  • 3b60984 change file locations based on feedback
  • 15b96a5 add documentation re: custom HTML extras template
  • 7d14e1c update per feedback
  • 06c3ed2 Merge branch 'master' into template_customizations

📊 Changes

5 files changed (+4 additions, -0 deletions)

View changed files

📝 docs/content/doc/advanced/customizing-gitea.en-us.md (+2 -0)
📝 templates/base/footer.tmpl (+1 -0)
📝 templates/base/head.tmpl (+1 -0)
➕ templates/custom/footer.tmpl (+0 -0)
➕ templates/custom/header.tmpl (+0 -0)

📄 Description

I have custom JS/CSS in use on my gitea instance and when I upgrade I have to edit head.tmpl and footer.tmpl to add in my changes again (otherwise I might have out of date templates). This will allow me to put all of my changes in header_extras.tmpl/footer_extras.tmpl and not worry about upgrading.

Open to suggestions regarding the names of the additional templates, or their locations.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-gitea/gitea/pull/3051 **Author:** [@techknowlogick](https://github.com/techknowlogick) **Created:** 12/1/2017 **Status:** ✅ Merged **Merged:** 12/3/2017 **Merged by:** [@lafriks](https://github.com/lafriks) **Base:** `master` ← **Head:** `template_customizations` --- ### 📝 Commits (5) - [`81c9ce9`](https://github.com/go-gitea/gitea/commit/81c9ce97c098066d5a15fd7be3931a4b5ead1176) Reduce overhead of upgrades for users with custom stylesheets/JS - [`3b60984`](https://github.com/go-gitea/gitea/commit/3b60984635deece024a5e9a0695f8de0d7981e48) change file locations based on feedback - [`15b96a5`](https://github.com/go-gitea/gitea/commit/15b96a570448f6812b8d8c07d3be8068e889017e) add documentation re: custom HTML extras template - [`7d14e1c`](https://github.com/go-gitea/gitea/commit/7d14e1cbd832421e154f25934232a3eafaf150fd) update per feedback - [`06c3ed2`](https://github.com/go-gitea/gitea/commit/06c3ed24a09f675516fbd9e4887541220a25834f) Merge branch 'master' into template_customizations ### 📊 Changes **5 files changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/doc/advanced/customizing-gitea.en-us.md` (+2 -0) 📝 `templates/base/footer.tmpl` (+1 -0) 📝 `templates/base/head.tmpl` (+1 -0) ➕ `templates/custom/footer.tmpl` (+0 -0) ➕ `templates/custom/header.tmpl` (+0 -0) </details> ### 📄 Description I have custom JS/CSS in use on my gitea instance and when I upgrade I have to edit head.tmpl and footer.tmpl to add in my changes again (otherwise I might have out of date templates). This will allow me to put all of my changes in header_extras.tmpl/footer_extras.tmpl and not worry about upgrading. Open to suggestions regarding the names of the additional templates, or their locations. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-02 12:17:42 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#16733
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?