forgejo/assets
silverwind b5d21c0adf
Generate go-licenses during tidy again (#21108)
We can not have the `frontend` target depend on golang because of they
way drone is set up. Move the `go-licenses` generation back into `tidy`
where it will now also be checked for consistency during `tidy-check`.

(I assume all `main` branch builds should currently fail [like
this](https://drone.gitea.io/go-gitea/gitea/60244/1/11)).

The reasony why it shouldn't be treated the same as for example `go
generate` is because output files are checked in. tidy is imho the
optimal target to run this after.

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2022-09-09 11:33:01 -04:00
..
emoji.json Go 1.19 format (#20758) 2022-08-30 21:15:45 -05:00
favicon.svg Add the possibility to allow the user to have a favicon which differs from the main logo (#18542) 2022-05-23 23:54:48 +08:00
go-licenses.json Generate go-licenses during tidy again (#21108) 2022-09-09 11:33:01 -04:00
logo.svg