-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Remove legacy template helper functions #34426
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
Conversation
should mark this as breaking? |
Let me add that. As then we'll remember to make note of it in release notes. |
No, I do not think so. Instead, we should avoid mentioning unnecessary "breakings" in the changelog, to avoid confusing end users. Most of the changes are not that breaking to most end users. Last time I have edited the 1.24 release changelog to clarify that most breakings won't affected end users, but my changes were reset by unknown editors & reasons. |
This is not a breaking change, but it should be mentioned in the changelog, as some users may have customized template files that reference these helper functions. |
* giteaofficial/main: Add a webhook push test for dev branch (go-gitea#34421) [skip ci] Updated translations via Crowdin Fix bug webhook milestone is not right. (go-gitea#34419) Only git operations should update `last changed` of a repository (go-gitea#34388) When updating comment, if the content is the same, just return and not update the databse (go-gitea#34422) Remove legacy template helper functions (go-gitea#34426) Fix GetUsersByEmails (go-gitea#34423) [skip ci] Updated translations via Crowdin Fix a bug when uploading file via lfs ssh command (go-gitea#34408) Merge and tweak markup editor expander CSS (go-gitea#34409) Bump `@github/relative-time-element` to v4.4.8 (go-gitea#34413) Refactor commit message rendering and fix bugs (go-gitea#34412)
These functions have been marked as
panicIfDevOrTesting
since 1.23 (#32422)