Generate go-licenses during tidy again (#21108)

Browse Source

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>

...

This commit is contained in:

silverwind

2022-09-09 17:33:01 +02:00

committed by GitHub

parent 86ed47e622

commit b5d21c0adf

4 changed files with 32 additions and 18 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

5

assets/go-licenses.json

File diff suppressed because one or more lines are too long