-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Add the possibility to allow the user to have a favicon which differs from the main logo #18542
Conversation
This allows the user to have a favicon which differs from the logo.
This is needed to accommodate the changes for allowing the user to have a differing logo and favicon
generate-images.js needs to be update to generate This is a breaking change for users of custom icons in any case because of the different HTTP filename. |
Also, you need to alter |
Co-authored-by: silverwind <[email protected]>
…ons.svg file This belongs to PR go-gitea#18542.
Hey @silverwind, adjusted that, makes total sense. The changes are also tested and work as intended. Regarding the breaking of currently customised favicons: |
as per the CONTRIBUTING.md: If your PR could cause a breaking change you must add a BREAKING section to the opening comment e.g.:
To explain how this could affect users and how to mitigate these changes. |
I've added a clearer description of how generate-images works now. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 months. Thank you for your contributions. |
Is there anything left to be done to get it included into 1.17.0? |
Maybe update the PR description once more with instructions for users that had used the previous single source file, e.g. that they now have to copy their |
Please resolve the conflicts |
@lunny Done, conflicts resolved. |
Thanks @je-s, the linting is failing on the head.tmpl due to mix use of tabs v spaces. If you have time to send a new commit to resolve I can merge now, otherwise I can update your branch later with the fix. |
@techknowlogick Should be fine now, done. |
Something is wrong with your merge, the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
merge needs to be fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocking until failed merge is fixed
@lafriks @silverwind Yeah, this old section got falsely included. I've removed the window.config script section to reflect the current state again. I think we should be good now finally. :) |
If there is nothing more left to do, this PR will be merged in 2 days (some more open days, in case some people want to improve it). |
* giteaofficial/main: [skip ci] Updated translations via Crowdin Add the possibility to allow the user to have a favicon which differs from the main logo (go-gitea#18542)
… from the main logo (go-gitea#18542) * Changed the filename of the favicon SVG This allows the user to have a favicon which differs from the logo. * Added favicon.svg This is needed to accommodate the changes for allowing the user to have a differing logo and favicon * Adjusted page to accommodate what icon is used as favicon * Added functionality to also generate the favicon.svg via generate-images.js * Adjusted the description for the new favicon compatibility Co-authored-by: silverwind <[email protected]> * Updated generate-images.js to generate favicons from a separate favicons.svg file This belongs to PR go-gitea#18542. * Added description on how custom favicons can be generated * Replaced space indents with tabs * Synced changes with current state of the file * Synced changes with current state of the file Co-authored-by: silverwind <[email protected]> Co-authored-by: zeripath <[email protected]> Co-authored-by: Lunny Xiao <[email protected]> Co-authored-by: Lauris BH <[email protected]>
This change breaks users' current favicon configuration. Since we're replacing the path in the HTML file, Gitea will fall back to the standard Gitea logo for the favicon.
In order to fix this, users need to re-run the steps described in Customizing Gitea.
In short: The users need to copy their current
logo.svg
tofavicon.svg
, re-runmake generate-images
, and place the files in the folder accordingly as described in the guide linked above.As described in #18541, this change allows the user to have a favicon which differs from his main logo.
In order to not break existing stuff, I've added/copied the icon.svg to favicon.svg. I've also adjusted the "Customizing Gitea" page already.